From: Greg KH <gregkh@suse.de>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: "Wolfgang Walter" <wolfgang.walter@stwm.de>,
linux-kernel@vger.kernel.org,
"Rick Koshi" <nfs-bug-report@more-right-rudder.com>,
"Ivo Přikryl" <prikryl@eurosat.cz>
Subject: Re: 2.6.38.2: regression from 2.6.38: kernel BUG at fs/nfsd/nfs4state.c:380!
Date: Mon, 28 Mar 2011 20:17:25 -0700 [thread overview]
Message-ID: <20110329031725.GA3665@suse.de> (raw)
In-Reply-To: <20110329031347.GC2695@fieldses.org>
On Mon, Mar 28, 2011 at 11:13:47PM -0400, J. Bruce Fields wrote:
> Bah, apologies about this, I don't know how it got through my own
> testing.
>
> On Mon, Mar 28, 2011 at 02:41:22PM -0700, Greg KH wrote:
> > On Mon, Mar 28, 2011 at 11:00:57PM +0200, Wolfgang Walter wrote:
> > > I just searched linux-nfs and found this:
> > >
> > > http://marc.info/?l=linux-nfs&m=130129644016061&w=4
> > >
> > > He even seems to have a real fix though I don't want to test it
> > > without blessing.
> >
> > Well, you aren't going to get that from me, Bruce?
>
> Good analysis from Mi Jinlong, but I'm not convinced by the patch....
>
> I'll look closer.
>
> (Disclaimer: between the sleep deprivation and the UM hospital's dubious
> guest wifi (hey, how's a new dad supposed to keep up with his kernel
> hacking if they block git?), I may be a little slow.)
Hey, no rush, you have more important things to deal with, I can always
revert the patch for now :)
thanks,
greg k-h
next prev parent reply other threads:[~2011-03-29 3:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-28 20:23 2.6.38.2: regression from 2.6.38: kernel BUG at fs/nfsd/nfs4state.c:380! Wolfgang Walter
2011-03-28 20:32 ` Greg KH
2011-03-28 21:00 ` Wolfgang Walter
2011-03-28 21:41 ` Greg KH
2011-03-29 3:13 ` J. Bruce Fields
2011-03-29 3:17 ` Greg KH [this message]
2011-04-11 8:17 ` J. Bruce Fields
2011-04-12 0:08 ` Greg KH
2011-04-16 0:41 ` J. Bruce Fields
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=20110329031725.GA3665@suse.de \
--to=gregkh@suse.de \
--cc=bfields@fieldses.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs-bug-report@more-right-rudder.com \
--cc=prikryl@eurosat.cz \
--cc=wolfgang.walter@stwm.de \
/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.