From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Andi Kleen <ak@suse.de>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: NFS mount gives ENETDOWN in -git15
Date: Sun, 22 Jul 2007 13:55:16 -0400 [thread overview]
Message-ID: <1185126916.6577.6.camel@localhost> (raw)
In-Reply-To: <200707211531.17750.ak@suse.de>
[-- Attachment #1: Type: text/plain, Size: 382 bytes --]
On Sat, 2007-07-21 at 15:31 +0200, Andi Kleen wrote:
> I tried to mount another nfs mount on a system running with nfsroot.
> But I get
>
> # mount basil:/home /basil/home/
> mount: Network is down
>
> The network is not down of course, the system is happily running with nfs root from that
> server. Userland is older SUSE 10.0
Does Al's patch help in any way?
Cheers
Trond
[-- Attachment #2: Attached message - [PATCH] fix broken handling of port=... in NFS option parsing --]
[-- Type: message/rfc822, Size: 2417 bytes --]
From: Al Viro <viro@ftp.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Chuck Lever <chuck.lever@oracle.com>, Trond Myklebust <Trond.Myklebust@netapp.com>, linux-kernel@vger.kernel.org
Subject: [PATCH] fix broken handling of port=... in NFS option parsing
Date: Sun, 22 Jul 2007 10:59:06 +0100
Message-ID: <20070722095906.GX21668@ftp.linux.org.uk>
Obviously broken on little-endian; fortunately, the option is
not frequently used...
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
---
diff --git a/fs/nfs/super.c b/fs/nfs/super.c
index b34b7a7..b2a851c 100644
--- a/fs/nfs/super.c
+++ b/fs/nfs/super.c
@@ -732,7 +732,7 @@ static int nfs_parse_mount_options(char *raw,
return 0;
if (option < 0 || option > 65535)
return 0;
- mnt->nfs_server.address.sin_port = htonl(option);
+ mnt->nfs_server.address.sin_port = htons(option);
break;
case Opt_rsize:
if (match_int(args, &mnt->rsize))
next prev parent reply other threads:[~2007-07-22 17:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-21 13:31 NFS mount gives ENETDOWN in -git15 Andi Kleen
2007-07-22 17:55 ` Trond Myklebust [this message]
2007-07-22 23:10 ` Yinghai Lu
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=1185126916.6577.6.camel@localhost \
--to=trond.myklebust@fys.uio.no \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).