From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jeff Layton <jeff.layton@primarydata.com>
Cc: linux-nfs@vger.kernel.org, Trond Myklebust <trondmy@gmail.com>,
Anna Schumaker <schumakeranna@gmail.com>
Subject: Re: BUG: [<ffffffffa01dac02>] nfsd4_proc_compound+0x432/0x6c0 [nfsd]
Date: Wed, 12 Nov 2014 11:53:32 -0500 [thread overview]
Message-ID: <20141112165332.GC5510@fieldses.org> (raw)
In-Reply-To: <20141112112821.22c15580@tlielax.poochiereds.net>
On Wed, Nov 12, 2014 at 11:28:21AM -0500, Jeff Layton wrote:
> On Wed, 12 Nov 2014 11:24:51 -0500
> "J. Bruce Fields" <bfields@fieldses.org> wrote:
>
> > On Wed, Nov 12, 2014 at 11:19:55AM -0500, Jeff Layton wrote:
> > > Hi Bruce,
> > >
> > > I've seen the following crash happen on a couple of different kernels
> > > recently. This one is from an older kernel that I just happened to be
> > > testing some other code on, but I've seen the same oops as well on
> > > v3.17.2 kernel from the fedora repos:
> >
> > Do you have 51904b08072a "nfsd4: fix crash on unknown operation number"
> > ?
> >
> > --b.
> >
>
> Ahh no...neither one has that. I'll apply it to the test kernel I'm
> using and see if it goes away. Thanks!
>
> That said...wonder what the client would be sending that would cause
> this to fire?
There was a mis-merge, and CAP_SEEK is set in the wrong place in
fs/nfs/nfs4proc.c. If you grep for CAP_SEEK in that file you'll see the
problem.
Trond, Anna, that still seems to be wrong upstream? What happened to
that fix?
--b.
prev parent reply other threads:[~2014-11-12 16:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-12 16:19 BUG: [<ffffffffa01dac02>] nfsd4_proc_compound+0x432/0x6c0 [nfsd] Jeff Layton
2014-11-12 16:24 ` J. Bruce Fields
2014-11-12 16:28 ` Jeff Layton
2014-11-12 16:53 ` J. Bruce Fields [this message]
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=20141112165332.GC5510@fieldses.org \
--to=bfields@fieldses.org \
--cc=jeff.layton@primarydata.com \
--cc=linux-nfs@vger.kernel.org \
--cc=schumakeranna@gmail.com \
--cc=trondmy@gmail.com \
/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.