From: Chris Mason <chris.mason@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Oleg Nesterov <oleg@redhat.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Matthew Wilcox <matthew@wil.cx>, Chuck Lever <cel@citi.umich.edu>,
Nick Piggin <nickpiggin@yahoo.com.au>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Ingo Molnar <mingo@elte.hu>,
stable@kernel.org
Subject: Re: [RFC v7] wait: prevent exclusive waiter starvation
Date: Mon, 02 Feb 2009 10:47:47 -0500 [thread overview]
Message-ID: <1233589667.18113.24.camel@think.oraclecorp.com> (raw)
In-Reply-To: <1233239675.10354.18.camel@think.oraclecorp.com>
On Thu, 2009-01-29 at 09:34 -0500, Chris Mason wrote:
> > > > So I think we're saying that
> > > > lock_page_killable-avoid-lost-wakeups.patch actually did fix the bug?
> > >
> > > I think yes,
> > >
>
> Our test case that was able to reliably trigger the bug was fixed by
> lock_page_killable-avoid-lost-wakeups.patch.
>
> I'll ask them to test v7 as well. The run takes about a day, so
> confirmation will take a bit.
v7 went through a total of 5 runs and passed all of them. Unpatched we
would fail after one run, so I think this does fix it.
-chris
WARNING: multiple messages have this Message-ID (diff)
From: Chris Mason <chris.mason@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Oleg Nesterov <oleg@redhat.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Matthew Wilcox <matthew@wil.cx>, Chuck Lever <cel@citi.umich.edu>,
Nick Piggin <nickpiggin@yahoo.com.au>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Ingo Molnar <mingo@elte.hu>,
stable@kernel.org
Subject: Re: [RFC v7] wait: prevent exclusive waiter starvation
Date: Mon, 02 Feb 2009 10:47:47 -0500 [thread overview]
Message-ID: <1233589667.18113.24.camel@think.oraclecorp.com> (raw)
In-Reply-To: <1233239675.10354.18.camel@think.oraclecorp.com>
On Thu, 2009-01-29 at 09:34 -0500, Chris Mason wrote:
> > > > So I think we're saying that
> > > > lock_page_killable-avoid-lost-wakeups.patch actually did fix the bug?
> > >
> > > I think yes,
> > >
>
> Our test case that was able to reliably trigger the bug was fixed by
> lock_page_killable-avoid-lost-wakeups.patch.
>
> I'll ask them to test v7 as well. The run takes about a day, so
> confirmation will take a bit.
v7 went through a total of 5 runs and passed all of them. Unpatched we
would fail after one run, so I think this does fix it.
-chris
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-02-02 15:49 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-17 21:51 + lock_page_killable-avoid-lost-wakeups.patch added to -mm tree Oleg Nesterov
2009-01-18 1:38 ` [PATCH v3] wait: prevent waiter starvation in __wait_on_bit_lock Johannes Weiner
2009-01-18 1:38 ` Johannes Weiner
2009-01-18 2:32 ` Oleg Nesterov
2009-01-18 2:32 ` Oleg Nesterov
2009-01-20 20:31 ` Johannes Weiner
2009-01-20 20:31 ` Johannes Weiner
2009-01-21 14:36 ` Oleg Nesterov
2009-01-21 14:36 ` Oleg Nesterov
2009-01-21 21:38 ` [RFC v4] " Johannes Weiner
2009-01-21 21:38 ` Johannes Weiner
2009-01-22 20:25 ` Oleg Nesterov
2009-01-22 20:25 ` Oleg Nesterov
2009-01-23 0:26 ` Dmitry Adamushko
2009-01-23 0:26 ` Dmitry Adamushko
2009-01-23 0:47 ` Oleg Nesterov
2009-01-23 0:47 ` Oleg Nesterov
2009-01-23 10:07 ` Dmitry Adamushko
2009-01-23 10:07 ` Dmitry Adamushko
2009-01-23 11:05 ` Oleg Nesterov
2009-01-23 11:05 ` Oleg Nesterov
2009-01-23 12:36 ` Dmitry Adamushko
2009-01-23 12:36 ` Dmitry Adamushko
2009-01-23 9:59 ` Johannes Weiner
2009-01-23 9:59 ` Johannes Weiner
2009-01-23 11:35 ` Oleg Nesterov
2009-01-23 11:35 ` Oleg Nesterov
2009-01-23 13:30 ` Oleg Nesterov
2009-01-23 13:30 ` Oleg Nesterov
2009-01-26 21:59 ` [RFC v5] wait: prevent exclusive waiter starvation Johannes Weiner
2009-01-26 21:59 ` Johannes Weiner
2009-01-27 3:23 ` Oleg Nesterov
2009-01-27 3:23 ` Oleg Nesterov
2009-01-27 19:34 ` [RFC v6] " Johannes Weiner
2009-01-27 19:34 ` Johannes Weiner
2009-01-27 20:05 ` Oleg Nesterov
2009-01-27 20:05 ` Oleg Nesterov
2009-01-27 22:31 ` Johannes Weiner
2009-01-27 22:31 ` Johannes Weiner
2009-01-28 9:14 ` [RFC v7] " Johannes Weiner
2009-01-28 9:14 ` Johannes Weiner
2009-01-29 4:42 ` Oleg Nesterov
2009-01-29 4:42 ` Oleg Nesterov
2009-01-29 7:37 ` Andrew Morton
2009-01-29 7:37 ` Andrew Morton
2009-01-29 8:31 ` Oleg Nesterov
2009-01-29 8:31 ` Oleg Nesterov
2009-01-29 9:11 ` Andrew Morton
2009-01-29 9:11 ` Andrew Morton
2009-01-29 14:34 ` Chris Mason
2009-01-29 14:34 ` Chris Mason
2009-02-02 15:47 ` Chris Mason [this message]
2009-02-02 15:47 ` Chris Mason
2009-01-23 19:24 ` [RFC v4] wait: prevent waiter starvation in __wait_on_bit_lock Johannes Weiner
2009-01-23 19:24 ` Johannes Weiner
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=1233589667.18113.24.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=cel@citi.umich.edu \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matthew@wil.cx \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=oleg@redhat.com \
--cc=stable@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.