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@xxxxxxxxxxxx> 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. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
