linux-kernel - Re: kernel BUG at fs/buffer.c:3205 (stable 3.5.3)

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: <506474E8.3030300@ahsoftware.de>
Date:	Thu, 27 Sep 2012 17:46:48 +0200
From:	Alexander Holler <holler@...oftware.de>
To:	Jan Kara <jack@...e.cz>
CC:	Dan Carpenter <dan.carpenter@...cle.com>,
	linux-kernel@...r.kernel.org
Subject: Re: kernel BUG at fs/buffer.c:3205 (stable 3.5.3)

Hello,

Am 27.09.2012 17:12, schrieb Jan Kara:
>    Just some thoughts about your oops:
> The assertion which fails is:
> BUG_ON(!list_empty(&bh->b_assoc_buffers));
>
> Now b_assoc_buffers isn't used very much. In particular ext4 which you seem
> to be using doesn't use this list at all (except when mounted in nojournal
> mode but that doesn't seem to be your case). That would point rather
> strongly at a memory corruption issue.
>
> So if you can reproduce the oops, it might be interesting to print
> bh->b_assoc_buffers.next and &bh->b_assoc_buffers.next if the list is found
> to be non-empty.

Hmm, a loose pointer would explain it all too. Especially the cases when 
I just have seen wrong content in the archive without having any oops. I 
try to reproduce it with

pr_info("AHO: %p %p\n", bh->b_assoc_buffers.next, 
&bh->b_assoc_buffers.next);

after the BUG_ON().

Thanks for the hint. I wasn't already that far to know that 
b_assoc_buffers isn't used that much.

Regards,

Alexander
--
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/