From: <Andries.Brouwer@cwi.nl>
To: akpm@osdl.org, torvalds@osdl.org, trond.myklebust@fys.uio.no
Cc: linux-kernel@vger.kernel.org
Subject: [patch] silence nfs mount messages
Date: Mon, 29 Mar 2004 21:00:54 +0200 (MEST) [thread overview]
Message-ID: <UTC200403291900.i2TJ0sC14336.aeb@smtp.cwi.nl> (raw)
People complain about the kernel messages when mounting NFS.
(Just like last time a new NFS version was introduced.)
It is perfectly normal to have mount newer than the kernel,
or the kernel newer than mount. No messages are needed or useful.
Andries
diff -uprN -X /linux/dontdiff a/fs/nfs/inode.c b/fs/nfs/inode.c
--- a/fs/nfs/inode.c 2004-02-18 11:33:18.000000000 +0100
+++ b/fs/nfs/inode.c 2004-03-29 20:53:28.000000000 +0200
@@ -1292,8 +1292,10 @@ static struct super_block *nfs_get_sb(st
memset(root->data+root->size, 0, sizeof(root->data)-root->size);
if (data->version != NFS_MOUNT_VERSION) {
+#if 0
printk("nfs warning: mount version %s than kernel\n",
data->version < NFS_MOUNT_VERSION ? "older" : "newer");
+#endif
if (data->version < 2)
data->namlen = 0;
if (data->version < 3)
@@ -1599,10 +1601,12 @@ static struct super_block *nfs4_get_sb(s
/* Zero out the NFS state stuff */
init_nfsv4_state(server);
+#if 0
if (data->version != NFS4_MOUNT_VERSION) {
printk("nfs warning: mount version %s than kernel\n",
data->version < NFS_MOUNT_VERSION ? "older" : "newer");
}
+#endif
p = nfs_copy_user_string(NULL, &data->hostname, 256);
if (IS_ERR(p))
next reply other threads:[~2004-03-29 19:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-29 19:00 Andries.Brouwer [this message]
2004-03-29 19:11 ` Trond Myklebust
2004-03-29 19:54 ` Andries Brouwer
2004-03-29 23:24 ` Trond Myklebust
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=UTC200403291900.i2TJ0sC14336.aeb@smtp.cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=trond.myklebust@fys.uio.no \
/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®