mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Andries Brouwer <Andries.Brouwer@cwi.nl>
Cc: Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [patch] silence nfs mount messages
Date: Mon, 29 Mar 2004 18:24:13 -0500	[thread overview]
Message-ID: <1080602653.2410.192.camel@lade.trondhjem.org> (raw)
In-Reply-To: <20040329195435.GA19426@apps.cwi.nl>

På må , 29/03/2004 klokka 14:54, skreiv Andries Brouwer:

> The features that are being used are used by layers of software.
> If there is information to be passed, it should be passed to
> that software, not printed in a syslog.
> It is not the kernel's job to set policy and have an opinion about user mode setup.

What do you mean "setting policy"? Your program is attempting to use an
obsolete kernel ABI. Of course it should "have an opinion" about that...

The issue is merely whether or not to issue an EINVAL, in order to force
users to upgrade to an updated version of "mount":
For 2.7.x, I'm rather of a mind to do just that in order to finally
clean up the wretched struct nfs_mount and eliminate all the unused
backward-compatibilty crap, but doing so in the middle of 2.6.x is not
an option (particularly given that the SELinux mount changes came as
late as they did).

Cheers,
  Trond

  reply	other threads:[~2004-03-29 23:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-29 19:00 Andries.Brouwer
2004-03-29 19:11 ` Trond Myklebust
2004-03-29 19:54   ` Andries Brouwer
2004-03-29 23:24     ` Trond Myklebust [this message]
2004-03-29 23:46       ` Andries Brouwer
2004-03-30  0:20         ` Trond Myklebust
2004-03-30  1:33           ` Andries Brouwer
2004-03-30  1:56             ` Trond Myklebust

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1080602653.2410.192.camel@lade.trondhjem.org \
    --to=trond.myklebust@fys.uio.no \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®