Subject: Re: [patch] silence nfs mount messages
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
In-Reply-To: <20040329195435.GA19426@apps.cwi.nl>
References: <UTC200403291900.i2TJ0sC14336.aeb@smtp.cwi.nl>
	 <1080587480.2410.61.camel@lade.trondhjem.org>
	 <20040329195435.GA19426@apps.cwi.nl>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8BIT
Message-Id: <1080602653.2410.192.camel@lade.trondhjem.org>
Mime-Version: 1.0
Date: Mon, 29 Mar 2004 18:24:13 -0500
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1143
Lines: 25

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/