From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Alexey Dobriyan <adobriyan@sw.ru>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.23-rc2-mm1: hang, prop_norm_single involved
Date: Thu, 09 Aug 2007 14:45:02 +0200 [thread overview]
Message-ID: <1186663502.20108.28.camel@twins> (raw)
In-Reply-To: <20070809111044.GA6575@localhost.sw.ru>
[-- Attachment #1: Type: text/plain, Size: 1102 bytes --]
On Thu, 2007-08-09 at 15:10 +0400, Alexey Dobriyan wrote:
> LTP run reproducably hangs during rwtest01 test
> rwtest -N rwtest01 -c -q -i 60s -f sync 10%25000:rs-sync=$$
> Calltrace is always the same:
>
> INFO: trying to register non-static key
> __lock_acquire+0x210/0xc9e
> lock_acquire+0x87/0xa3
> _spin_lock_irqsave+0x2f/0x5f
> prop_norm_single+0x32/0x74
> set_page_dirty+0xd6/0x151
> set_page_dirty_balance+0xc/0x71
> do_wp_page+0x4ae/0x52b
> handle_mm_fault+0x616/0x6c4
> do_page_fault+0x1b0/0x51c
[root@opteron ~]# PATH=/testcases/bin/:$PATH /testcases/bin/rwtest -N rwtest01 -c -q -i 60s -f sync 10%25000:rs-sync=$$
rwtest01 1 PASS : Test passed
[root@opteron ~]# PATH=/testcases/bin/:$PATH /testcases/bin/rwtest -N rwtest01 -c -q -i 60s -f sync 10%25000:rs-sync=$$
I can reproduce, but not always.
Also, since the task->dirties member is initialized in fork.c this
should either _always_ happen or never. So this does point to some
memory corruption, ->dirties is the very last member of the task struct.
/me goes try with slab_debug,...
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-08-09 12:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-09 11:10 2.6.23-rc2-mm1: hang, prop_norm_single involved Alexey Dobriyan
2007-08-09 12:45 ` Peter Zijlstra [this message]
2007-08-09 15:30 ` Peter Zijlstra
2007-08-09 12:51 ` Cornelia Huck
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=1186663502.20108.28.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=adobriyan@sw.ru \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.