From: "J. Bruce Fields" <bfields@fieldses.org>
To: richard@vdtoorn.nl
Cc: linux-nfs@vger.kernel.org
Subject: Re: Hanging nfs4+krb5 mounts with negative uids?
Date: Mon, 21 Jan 2013 15:00:00 -0500 [thread overview]
Message-ID: <20130121200000.GA1820@fieldses.org> (raw)
In-Reply-To: <c7d3923f1438a9217cfbb53744b5be21.squirrel@vdtoorn.nl>
On Mon, Jan 21, 2013 at 08:38:16PM +0100, richard@vdtoorn.nl wrote:
> Hi Bruce,
>
> Well done! Your answer to upgrade to a later version of the kernel fixed
> the problem. I tested this on kernel 3.7.3 and it works beautifully.
Thanks for confirming.--b.
>
> Thanks very much!
>
> Richard
>
> >> This code gets hit, e.g. with the new debian stable release where
> >> nfs-kernel-server/nfs-common is upgraded to 1.2.6-3 (or upgrade
> >> nfs-kernel-server from debian stable to debian unstable). On my
> >> nfsv4+krb5
> >> system, this seems to do exactly the opposite of the patch: not fixing,
> >> but in fact introducing a hanging mount.
> >>
> >> When I change the code back from unsigned uid's to signed uid's the
> >> mount
> >> works again.
> >
> > Assuming you're running kernel 3.7--this shoulds like the problem fixed
> > by kernel commit 621eb19ce1ec.. "svcrpc: Revert "sunrpc/cache.h: replace
> > simple_strtoul"", which has also been backported to 3.7.3. Could you
> > let us know whether applying that patch, or upgrading to 3.7.3, fixes
> > the problem?
> >
> > --b.
>
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-01-21 20:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-21 15:07 Hanging nfs4+krb5 mounts with negative uids? richard
2013-01-21 16:05 ` richard
2013-01-21 16:11 ` J. Bruce Fields
2013-01-21 19:38 ` richard
2013-01-21 20:00 ` J. Bruce Fields [this message]
2013-01-22 16:47 ` Sven Geggus
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=20130121200000.GA1820@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=richard@vdtoorn.nl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.