From: Greg Dietsche <greg@gregd.org>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: 3.0 rc3 bug & warning fs/inode.c && fs/fs-writeback.c
Date: Tue, 21 Jun 2011 17:21:19 -0500 [thread overview]
Message-ID: <4E01195F.8040000@gregd.org> (raw)
In-Reply-To: <20110621124556.GZ11521@ZenIV.linux.org.uk>
On 06/21/2011 07:45 AM, Al Viro wrote:
> On Tue, Jun 21, 2011 at 07:25:52AM -0500, Greg Dietsche wrote:
>> from the just missed rc4 department:
>> I recieved this BUG last night on my laptop and it was shortly
>> followed by a warning from the kernel. I doubt that I can reproduce
>> this. It happened under a light load. I was doing some emailing
>> using thunderbird (er.... icedove.....). let me know if there's
>> anything I can do to help debug or if there's more info I can get
>> that would help you figure out what went wrong.
>
> Which filesystems had been mounted? That looks like a stray pointer
> to struct inode (i.e. outliving the inode eviction on final iput());
> might be the one fixed by commit 50338b889dc504c69e0cb316ac92d1b9e51f3c8a,
> might be something else...
>
I'm leaning towards might be something else. Correct me if I'm wrong,
but it seems that 50338b889dc504c69e0cb316ac92d1b9e51f3c8a was included
in rc3.
thanks,
Greg
next prev parent reply other threads:[~2011-06-21 22:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 12:25 3.0 rc3 bug & warning fs/inode.c && fs/fs-writeback.c Greg Dietsche
2011-06-21 12:45 ` Al Viro
2011-06-21 12:54 ` Greg Dietsche
2011-06-21 22:21 ` Greg Dietsche [this message]
2011-06-21 22:40 ` Al Viro
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=4E01195F.8040000@gregd.org \
--to=greg@gregd.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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).