linux-kernel - Re: 3.0 rc3 bug & warning fs/inode.c && fs/fs-writeback.c

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4E01195F.8040000@gregd.org>
Date:	Tue, 21 Jun 2011 17:21:19 -0500
From:	Greg Dietsche <greg@...gd.org>
To:	Al Viro <viro@...IV.linux.org.uk>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	linux-fsdevel@...r.kernel.org
Subject: Re: 3.0 rc3 bug & warning fs/inode.c && fs/fs-writeback.c

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/