lkml.org 
[lkml]   [2012]   [Sep]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: kernel BUG at fs/buffer.c:3205 (stable 3.5.3)
On Thu 27-09-12 17:46:48, Alexander Holler wrote:
> 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().
It should have been:
if (!list_empty(&bh->b_assoc_buffers))
pr_info("AHO: %p %p\n", bh->b_assoc_buffers.next,
&bh->b_assoc_buffers.next);
*before* BUG_ON().

What you saw in the logs were just pointers showing the list is empty
(naturally as otherwise we'd see the BUG_ON trigger).

Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR


\
 
 \ /
  Last update: 2012-09-27 22:41    [W:0.075 / U:0.304 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site