From: Bryan Schumaker <bjschuma@netapp.com>
To: Eric Paris <eparis@redhat.com>
Cc: linux-nfs@vger.kernel.org, Trond.Myklebust@netapp.com
Subject: Re: [REGRESSION] 8f70e95f9f4159184f557 causes mount failure with EGAIN
Date: Wed, 30 Mar 2011 17:12:15 -0400 [thread overview]
Message-ID: <4D939CAF.40506@netapp.com> (raw)
In-Reply-To: <1301513561.561.7.camel@unknown001a4b0c2895>
On 03/30/2011 03:32 PM, Eric Paris wrote:
> $ git bisect good
> 8f70e95f9f4159184f557a1db60c909d7c1bd2e3 is the first bad commit
> commit 8f70e95f9f4159184f557a1db60c909d7c1bd2e3
> Author: Bryan Schumaker <bjschuma@netapp.com>
> Date: Thu Mar 24 17:12:31 2011 +0000
>
> NFS: Determine initial mount security
>
> When sec=<something> is not presented as a mount option,
> we should attempt to determine what security flavor the
> server is using.
>
> Signed-off-by: Bryan Schumaker <bjschuma@netapp.com>
> Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
>
> Using a linux-next kernel for the last 2 days I have been unable to
> mount exports from my RHEL6 server. mount(2) returned EAGAIN. Turned
Thanks for letting me know. What does your exports file look like?
Bryan
> up debugging (thanks jlayton) and got:
>
> [ 1732.795056] NFS: nfs mount opts='tcp,vers=4,addr=10.11.231.241,clientaddr=10.11.231.191'
> [ 1732.798079] NFS: parsing nfs mount option 'tcp'
> [ 1732.800210] NFS: parsing nfs mount option 'vers=4'
> [ 1732.802324] NFS: parsing nfs mount option 'addr=10.11.231.241'
> [ 1732.804477] NFS: parsing nfs mount option 'clientaddr=10.11.231.191'
> [ 1732.805790] NFS: MNTPATH: '/export/'
> [ 1732.806663] --> nfs4_try_mount()
> [ 1732.807459] --> nfs4_create_server()
> [ 1732.808301] --> nfs4_init_server()
> [ 1732.809136] --> nfs4_set_client()
> [ 1732.809898] --> nfs_get_client(paris.rdu.redhat.com,v4)
> [ 1732.811122] NFS: get client cookie (0xffff880039cfd9e8/0xffff88003b889000)
> [ 1732.813771] NFS: Callback listener port = 36700 (af 2)
> [ 1732.814931] NFS: Callback listener port = 60202 (af 10)
> [ 1732.816199] --> nfs_get_client() = ffff880039cfd9e8 [new]
> [ 1732.817356] <-- nfs4_set_client() = 0 [new ffff880039cfd9e8]
> [ 1732.818587] <-- nfs4_init_server() = 0
> [ 1732.819476] --> nfs4_get_rootfh()
> [ 1732.820282] encode_compound: tag=
> [ 1732.822070] encode_compound: tag=
> [ 1732.822937] nfs4_get_rootfh: getroot error = 11
> [ 1732.823982] <-- nfs4_get_rootfh() = -11
> [ 1732.824880] --> nfs_free_server()
> [ 1732.846219] --> nfs_put_client({1})
> [ 1732.847888] --> nfs_free_client(4)
> [ 1732.850236] NFS: releasing client cookie (0xffff880039cfd9e8/0xffff88003b889000)
> [ 1732.853726] <-- nfs_free_client()
> [ 1732.854505] <-- nfs_free_server()
> [ 1732.855274] <-- nfs4_create_server() = error -11
> [ 1732.856187] <-- nfs4_try_mount() = -11 [error]
>
> Bisected and got the commit listed above.
>
next prev parent reply other threads:[~2011-03-30 21:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 19:32 [REGRESSION] 8f70e95f9f4159184f557 causes mount failure with EGAIN Eric Paris
2011-03-30 21:12 ` Bryan Schumaker [this message]
2011-03-30 21:33 ` Eric Paris
2011-03-31 1:31 ` Eric Paris
2011-03-31 17:17 ` Bryan Schumaker
2011-04-02 19:01 ` J. Bruce Fields
2011-04-04 12:48 ` Bryan Schumaker
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=4D939CAF.40506@netapp.com \
--to=bjschuma@netapp.com \
--cc=Trond.Myklebust@netapp.com \
--cc=eparis@redhat.com \
--cc=linux-nfs@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).