public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Alexey Dobriyan <adobriyan@sw.ru>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, apw <apw@shadowen.org>
Subject: Re: 2.6.23-rc2-mm1: hang, prop_norm_single involved
Date: Thu, 09 Aug 2007 17:30:32 +0200	[thread overview]
Message-ID: <1186673432.20108.32.camel@twins> (raw)
In-Reply-To: <1186663502.20108.28.camel@twins>

On Thu, 2007-08-09 at 14:45 +0200, Peter Zijlstra wrote:
> 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:
> > 

> [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,...

to no avail, banging head against the wall what is happening here.

Andrew, could you:

# mm-dirty-balancing-for-tasks.patch

while I try to figure this one out?

That seems to make the unhappies I could reproduce here go away.


  reply	other threads:[~2007-08-09 15:32 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
2007-08-09 15:30   ` Peter Zijlstra [this message]
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=1186673432.20108.32.camel@twins \
    --to=peterz@infradead.org \
    --cc=adobriyan@sw.ru \
    --cc=akpm@osdl.org \
    --cc=apw@shadowen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox