From: Al Viro <viro@ZenIV.linux.org.uk>
To: Jun'ichi Nomura <j-nomura@ce.jp.nec.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Valdis.Kletnieks@vt.edu, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-s390@vger.kernel.org,
linux-next@vger.kernel.org,
Heiko Carstens <heiko.carstens@de.ibm.com>
Subject: Re: mmotm 2010-02-10 - BUG at fs/dcache.c:677!
Date: Fri, 12 Feb 2010 05:01:04 +0000 [thread overview]
Message-ID: <20100212050104.GS30031@ZenIV.linux.org.uk> (raw)
In-Reply-To: <4B74DE40.5030401@ce.jp.nec.com>
On Fri, Feb 12, 2010 at 01:51:12PM +0900, Jun'ichi Nomura wrote:
> (02/12/10 12:14), Andrew Morton wrote:
> > On Thu, 11 Feb 2010 21:44:17 -0500 Valdis.Kletnieks@vt.edu wrote:
> >
> >> On Wed, 10 Feb 2010 16:17:41 PST, akpm@linux-foundation.org said:
> >>> The mm-of-the-moment snapshot 2010-02-10-16-17 has been uploaded to
> >>>
> >>> http://userweb.kernel.org/~akpm/mmotm/
> >>
> >> Hit this at shutdown. ext4 filesystems. Brought it up to single-user
> >> mode, then 'shutdown -h now'.
> >>
> >> [ 58.311786] ------------[ cut here ]------------
> >> [ 58.312261] kernel BUG at fs/dcache.c:677!
> ...
>
> > Yeah, Sachin reported that against linux-next too (I think - need to
> > check the exact line numbers):
> > http://permalink.gmane.org/gmane.linux.file-systems/38148
> >
> > It seems to have been met with shrugs thus far.
>
> According to the Sachin's report:
> > While running hackbench against today's next-20100208 (9056d31..)
> > on a s390 box, came across following BUG.
> ...
> > Did not observe this with next-20100205. Also there doesn't seem to be
> > any patches applied to this code after the last release. So not
> > sure what could have caused this. Corresponding code is :
>
> So the bug seems introduced between next-20100205 and next-20100208.
>
> Isn't this change missing the equivalent of "dput(old)"?
Argh... Nice catch, and yes, it is.
next prev parent reply other threads:[~2010-02-12 5:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201002110043.o1B0hKxW008835@imap1.linux-foundation.org>
[not found] ` <8576.1265942657@localhost>
2010-02-12 3:14 ` mmotm 2010-02-10 - BUG at fs/dcache.c:677! Andrew Morton
2010-02-12 4:51 ` Jun'ichi Nomura
2010-02-12 5:01 ` Al Viro [this message]
2010-02-12 5:07 ` Al Viro
2010-02-12 5:30 ` Stephen Rothwell
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=20100212050104.GS30031@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=heiko.carstens@de.ibm.com \
--cc=j-nomura@ce.jp.nec.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).