From: Chris Mason <chris.mason@oracle.com>
To: linux-mm@kvack.org
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Matthew Wilcox <matthew@wil.cx>,
"chuck.lever" <chuck.lever@oracle.com>
Subject: Re: [PATCH RFC] Lost wakeups from lock_page_killable()
Date: Wed, 14 Jan 2009 16:55:31 -0500 [thread overview]
Message-ID: <1231970131.8269.52.camel@think.oraclecorp.com> (raw)
In-Reply-To: <1231964632.8269.47.camel@think.oraclecorp.com>
On Wed, 2009-01-14 at 15:23 -0500, Chris Mason wrote:
> The patch below is entirely untested but may do a better job of
> explaining what I think the bug is. I'm hoping I can trigger it locally
> with a few dd commands mixed with a lot of kill commands.
>
I've tried many variations but haven't hit it locally yet. Hopefully
testers at oracle can confirm the patch fixes things for them, but the
runs take about a day.
-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-01-14 21:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 20:23 [PATCH RFC] Lost wakeups from lock_page_killable() Chris Mason
2009-01-14 21:55 ` Chris Mason [this message]
2009-01-14 22:30 ` Matthew Wilcox
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=1231970131.8269.52.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=a.p.zijlstra@chello.nl \
--cc=chuck.lever@oracle.com \
--cc=linux-mm@kvack.org \
--cc=matthew@wil.cx \
/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;
as well as URLs for NNTP newsgroup(s).