public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Zan Lynx <zlynx@acm.org>
To: Nick Piggin <nickpiggin@yahoo.com.au>
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: Mon, 23 Jun 2008 17:48:47 -0600	[thread overview]
Message-ID: <4860365F.5000609@acm.org> (raw)
In-Reply-To: <200806231229.42943.nickpiggin@yahoo.com.au>

Nick Piggin wrote:
> On Monday 23 June 2008 01:18, Ryan Hope wrote:
>> Well in the current version of the patchset we are using, one user
>> would start playing some game (disabling "Disable Heap Randomization"
>> fixed the hardlocks for him... the other user got hardlocks when
>> copying an ISO from a reiser4 partition to a reiserfs partition
>> (disabling swap fixed the issue for him).
> 
> Hmm, nobody has reported such a hang with -mm yet, so maybe it
> is another interaction in the patchset. OTOH, probably nobody
> much uses -mm and reiser4, and reiser4 does lots of weird fiddling
> with pagecache so it could be broken in -mm even.

I have been running and testing -mm with reiser4 for a couple years now.
 I haven't been able to run -mm recently because I've been hitting the
copy_user bug Linus fixed for AMD64 but Andrew hasn't updated yet (no
complaints, Andrew) and I'm too lazy to manually patch.

      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
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 [this message]

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=4860365F.5000609@acm.org \
    --to=zlynx@acm.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox