From: Christoph Lameter <clameter@sgi.com>
To: Miles Lane <miles.lane@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: 2.6.25-rc8-mm1 -- BUG buffer_head: Redzone overwritten
Date: Wed, 2 Apr 2008 20:31:20 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0804022016160.1510@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <47F43B7F.6090505@gmail.com>
On Wed, 2 Apr 2008, Miles Lane wrote:
> I hit the Redzone BUG while stress testing. I had several processes
> intensively reading my Windows NTFS partition and other processes reading from
> my ext3 partition. In addition, I was playing music residing on my NTFS
> partition using Rhythmbox. Lastly, the BUG occurred when I ran "apt-get
> update".
Hmmm... It looks like all the object fields of the object were
overwritten. Maybe one symptom of whatever cause the lock imbalance.
> [ 58.512165] [<f8b7dfd8>] snd_hda_multi_out_analog_open+0xd3/0xef
Could be related to sound driver issue? snd_hda seem to occurt in multiple
traces.
> [11543.669966]
> =============================================================================
> [11543.669979] BUG buffer_head: Redzone overwritten
Well thats nasty thing....
> [11543.669992] INFO: 0xd62af5d4-0xd62af5d7. First byte 0x5a instead of 0xbb
Was overwrittten with 5a inuse poison instead of red zone inactive. Could
be that the redone was not initialized.
> [11543.669997] INFO: Allocated in 0x5a5a5a5a age=2783036320 cpu=1515870810
> pid=1515870810
> [11543.670023] INFO: Freed in 0x5a5a5a5a age=2783036320 cpu=1515870810
> pid=1515870810
Bogus info because the metadata of the object was corrupted too.
> [11543.670036] INFO: Slab 0xc14db748 objects=42 used=23 fp=0xd62af5a0
> flags=0x150000c3
> [11543.670041] INFO: Object 0xd62af5a0 @offset=1440 fp=0x5a5a5a5a
> [11543.670044]
> [11543.670048] Bytes b4 0xd62af590: 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a
> 5a 5a ZZZZZZZZZZZZZZZZ
> [11543.670078] Object 0xd62af5a0: 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a
> 5a 5a ZZZZZZZZZZZZZZZZ
> [11543.670108] Object 0xd62af5b0: 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a
> 5a 5a ZZZZZZZZZZZZZZZZ
> [11543.670137] Object 0xd62af5c0: 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a
> 5a 5a ZZZZZZZZZZZZZZZZ
> [11543.670166] Object 0xd62af5d0: 5a 5a 5a 5a
Looks like a newly allocated object.
> ZZZZ [11543.670195] Redzone 0xd62af5d4: 5a 5a 5a 5a
> ZZZZ [11543.670223] Padding 0xd62af5fc: 5a 5a 5a 5a
But somehow padding and redzone were never set or overwritten?
> ondemand_readahead+0x11a/0x128
> [11543.670494] [page_cache_async_readahead+0x53/0x5e]
> page_cache_async_readahead+0x53/0x5e
> [11543.670507] [fuse:generic_file_aio_read+0x1ef/0x650]
> generic_file_aio_read+0x1ef/0x493
> [11543.670533] [fuse:do_sync_read+0xbb/0x8c3] do_sync_read+0xbb/0xf9
> [11543.670552] [<c0130fc5>] ? autoremove_wake_function+0x0/0x30
> [11543.670568] [snd_hda_intel:_spin_unlock_irqrestore+0x56/0x6c] ?
> _spin_unlock_irqrestore+0x56/0x6c
sound driver going to fuse?
> CONFIG_SLUB_DEBUG_ON=y
Ah. The command line possibility is not used.
next prev parent reply other threads:[~2008-04-03 3:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-03 2:05 Miles Lane
2008-04-03 3:31 ` Christoph Lameter [this message]
2008-04-03 10:26 ` Miklos Szeredi
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=Pine.LNX.4.64.0804022016160.1510@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miles.lane@gmail.com \
/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
all inboxes | Powered by JetHome®