From: Nick Piggin <nickpiggin@yahoo.com.au>
To: paulmck@linux.vnet.ibm.com
Cc: Ryan Hope <rmh3093@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-mm@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] Lockless patches cause hardlock under heavy IO
Date: Tue, 24 Jun 2008 10:13:45 +1000 [thread overview]
Message-ID: <200806241013.45908.nickpiggin@yahoo.com.au> (raw)
In-Reply-To: <20080623130536.GA10595@linux.vnet.ibm.com>
On Monday 23 June 2008 23:05, Paul E. McKenney wrote:
> On Mon, Jun 23, 2008 at 09:54:52PM +1000, Nick Piggin wrote:
> > On Monday 23 June 2008 13:51, Ryan Hope wrote:
> > > well i get the hardlock on -mm with out using reiser4, i am pretty
> > > sure is swap related
> >
> > The guys seeing hangs don't use PREEMPT_RCU, do they?
> >
> > In my swapping tests, I found -mm3 to be stable with classic RCU, but
> > on a hunch, I tried PREEMPT_RCU and it crashed a couple of times rather
> > quickly. First crash was in find_get_pages so I suspected lockless
> > pagecache doing something subtly wrong with the RCU API, but I just got
> > another crash in __d_lookup:
>
> Could you please send me a repeat-by? (At least Alexey is no longer
> alone!)
OK, I had DEBUG_PAGEALLOC in the .config, which I think is probably
important to reproduce it (but the fact that I'm reproducing oopses
with << PAGE_SIZE objects like dentries and radix tree nodes indicates
that there is even more free-before-grace activity going undetected --
if you construct a test case using full pages, it might become even
easier to detect with DEBUG_PAGEALLOC).
2 socket, 8 core x86 system.
I mounted two tmpfs filesystems, one contains a single large file
which is formatted as 1K block size ext3 and mounted loopback, the
other is used directly. Linux kernel source is unpacked on each mount
and concurrent make -j128 on each. This pushes it pretty hard into
swap. Classic RCU survived another 5 hours of this last night.
But that's a fairly convoluted test for an RCU problem. I expect it
should be easier to trigger with something more targetted...
next prev parent reply other threads:[~2008-06-24 0:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-18 21:15 [BUG] Lockless patches cause hardlock under heavy IO Ryan Hope
2008-06-18 21:28 ` Arjan van de Ven
2008-06-19 14:45 ` Ryan Hope
2008-06-20 0:05 ` Arjan van de Ven
2008-06-19 8:12 ` Peter Zijlstra
2008-06-19 8:19 ` Nick Piggin
2008-06-19 14:52 ` Ryan Hope
2008-06-19 20:31 ` Ryan Hope
2008-06-20 14:33 ` Ryan Hope
2008-06-22 14:37 ` Ryan Hope
2008-06-22 15:07 ` Peter Zijlstra
2008-06-22 15:18 ` Ryan Hope
2008-06-23 2:29 ` Nick Piggin
2008-06-23 3:51 ` Ryan Hope
2008-06-23 3:56 ` Nick Piggin
2008-06-23 11:54 ` Nick Piggin
2008-06-23 13:05 ` Paul E. McKenney
2008-06-24 0:13 ` Nick Piggin [this message]
2008-06-24 15:12 ` Ryan Hope
2008-06-24 15:32 ` Paul E. McKenney
2008-06-24 15:57 ` Ryan Hope
2008-06-24 16:12 ` Paul E. McKenney
2008-06-24 16:23 ` Ryan Hope
2008-06-24 18:01 ` Ryan Hope
2008-06-23 23:48 ` Zan Lynx
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=200806241013.45908.nickpiggin@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rmh3093@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 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.