From: "J. Bruce Fields" <bfields@fieldses.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: Tino Keitel <tino.keitel@tikei.de>, Neil Brown <neilb@suse.de>,
Trond Myklebust <Trond.Myklebust@netapp.com>,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.38-rc3: kernel BUG at fs/nfsd/nfs4state.c:3132!
Date: Fri, 11 Feb 2011 10:37:02 -0500 [thread overview]
Message-ID: <20110211153702.GC3005@fieldses.org> (raw)
In-Reply-To: <s5h62sqbnd7.wl%tiwai@suse.de>
On Fri, Feb 11, 2011 at 04:29:56PM +0100, Takashi Iwai wrote:
> At Fri, 11 Feb 2011 10:21:12 -0500,
> J. Bruce Fields wrote:
> > Again, 2.6.38-rc4 does not have a BUG() on line 3132. Could you post
> > the full oops message from your machine?
>
> Well, on vanilla 2.6.38-rc4, it's in nfs4_preprocess_stateid_op():
> if (filpp) {
> *filpp = find_readable_file(dp->dl_file);
> ==> BUG_ON(!*filpp);
> }
Oh good grief, my apologies--I mistyped "38" as "28"!
This looks like it could be a known delegation bug.... Would it be
possible for you to check whether this is reproduceable on
git://linux-nfs.org/~bfields/topics.git for-2.6.38-incoming
?
--b.
next prev parent reply other threads:[~2011-02-11 15:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110208221235.GA16984@mac.home>
2011-02-11 9:38 ` 2.6.38-rc3: kernel BUG at fs/nfsd/nfs4state.c:3132! Takashi Iwai
2011-02-11 15:21 ` J. Bruce Fields
2011-02-11 15:29 ` Takashi Iwai
2011-02-11 15:37 ` J. Bruce Fields [this message]
2011-02-11 16:01 ` Takashi Iwai
2011-02-11 16:05 ` J. Bruce Fields
2011-02-11 16:12 ` Takashi Iwai
2011-02-11 16:57 ` Takashi Iwai
2011-02-11 16:59 ` Takashi Iwai
2011-02-11 17:00 ` J. Bruce Fields
2011-02-11 17:43 ` J. Bruce Fields
2011-02-11 18:15 ` Takashi Iwai
2011-02-14 11:35 ` Takashi Iwai
2011-02-14 14:29 ` J. Bruce Fields
2011-02-11 17:00 ` J. Bruce Fields
2011-02-09 22:04 Tino Keitel
2011-02-10 21:36 ` J. Bruce Fields
2011-02-10 21:49 ` Tino Keitel
2011-02-10 23:41 ` Tino Keitel
2011-02-15 1:08 ` 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=20110211153702.GC3005@fieldses.org \
--to=bfields@fieldses.org \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=tino.keitel@tikei.de \
--cc=tiwai@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox