public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>,
	Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@elte.hu>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.15-rt20, "bad page state", jackd
Date: Thu, 09 Mar 2006 20:05:25 +1100	[thread overview]
Message-ID: <440FEFD5.6040104@yahoo.com.au> (raw)
In-Reply-To: <20060309084746.GB9408@osiris.boeblingen.de.ibm.com>

Heiko Carstens wrote:

> Actually I have a bug report that looks quite the same. Happens on s390x
> with lots of I/O stress. But that is against vanilla 2.6.16-rc4 + additional
> patches. I need to ask to reproduce that with a plain vanilla kernel, so
> that a git bisect search might help to figure out what is wrong.
> Unfortunately it seems to take hours before we hit the bug.
> 

It is different because yours is coming from __alloc_pages, so if there
are no previous warnings then it means it wasn't corrupted before last
being freed, so it is a use-after-free bug. I'm surprised at how many
fields have been modified though (mapping, count, mapcount).

PG_error is set, which might mean it is a bug in an error handling path
that doesn't trigger very often.

> <0>Bad page state in process 'blast'
> <0>page:0000000000507d00 flags:0x000000060000002a mapping:00000000007570b0 mapcount:1 count:8
> <0>Trying to fix it up, but a reboot is needed
> <0>Backtrace:
> <4>0000000006e93750 0000000000000000 0000000000773780 0700000000007c7a 
> <4>       0000000000000001 000000000025f878 000000000025f878 0000000000104840 
> <4>       0000000000000000 000000060000002a 0000000000000000 0000000000518d50 
> <4>       000000000000000c 0000000000000008 0000000006e936f8 0000000006e93770 
> <4>       000000000044e1f0 0000000000104840 0000000006e936f8 0000000006e93738 
> <4>Call Trace:
> <4>([<0000000000104870>] dump_stack+0x2b8/0x374)
> <4> [<00000000001a97de>] get_page_from_freelist+0x72e/0x8e8
> <4> [<00000000001a9aa8>] __alloc_pages+0x110/0x324
> <4> [<00000000001b37a0>] page_cache_readahead+0xf6c/0x11e4
> <4> [<000000000019f870>] do_generic_mapping_read+0x150/0x828
> <4> [<00000000001a07f4>] generic_file_aio_read+0x1f8/0x258
> <4> [<00000000001fa844>] do_sync_read+0x130/0x1bc
> <4> [<00000000001fc230>] sys_read+0x170/0x3b8
> <4> [<000000000010fb20>] sysc_tracego+0xe/0x14
> <4> [<0000020000043a84>] 0x20000043a84
> 
> Heiko

-- 
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com 

  reply	other threads:[~2006-03-09  9:07 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-08 19:36 2.6.15-rt20, "bad page state", jackd Fernando Lopez-Lezcano
2006-03-08 21:48 ` Fernando Lopez-Lezcano
2006-03-09  0:30   ` Fernando Lopez-Lezcano
2006-03-09  2:19     ` Fernando Lopez-Lezcano
2006-03-09  8:47 ` Heiko Carstens
2006-03-09  9:05   ` Nick Piggin [this message]
2006-03-09 21:08   ` Fernando Lopez-Lezcano
2006-03-09 22:57     ` Nick Piggin
2006-03-10  2:47       ` Fernando Lopez-Lezcano
2006-03-10  5:08         ` Nick Piggin
2006-03-10 18:50           ` [Alsa-devel] " Fernando Lopez-Lezcano
2006-03-10 23:10             ` Fernando Lopez-Lezcano
2006-03-11  0:01             ` Nick Piggin
2006-03-13  0:49               ` [Alsa-devel] Re: 2.6.15-rt20, "bad page state", jackd (alsa 1.0.10 vs. recent kernels) Fernando Lopez-Lezcano
2006-03-13  2:42                 ` Nick Piggin
2006-03-13  3:26                   ` Fernando Lopez-Lezcano
2006-03-13  3:31                     ` Lee Revell
2006-03-13  3:39                       ` Fernando Lopez-Lezcano
2006-03-13  3:53                         ` Lee Revell
2006-03-13 11:05                           ` Takashi Iwai
2006-03-13 17:33                             ` Fernando Lopez-Lezcano
2006-03-13 17:41                               ` Takashi Iwai
2006-03-13  9:25                 ` Ingo Molnar

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=440FEFD5.6040104@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nando@ccrma.Stanford.EDU \
    --cc=rostedt@goodmis.org \
    /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