From: Oleg Nesterov <oleg@redhat.com>
To: Chris Mason <chris.mason@oracle.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Matthew Wilcox <matthew@wil.cx>, Chuck Lever <cel@citi.umich.edu>,
Nick Piggin <nickpiggin@yahoo.com.au>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: + lock_page_killable-avoid-lost-wakeups.patch added to -mm tree
Date: Sat, 17 Jan 2009 22:51:10 +0100 [thread overview]
Message-ID: <20090117215110.GA3300@redhat.com> (raw)
I think the patch is correct, just a question,
> int __lock_page_killable(struct page *page)
> {
> DEFINE_WAIT_BIT(wait, &page->flags, PG_locked);
> + int ret;
>
> - return __wait_on_bit_lock(page_waitqueue(page), &wait,
> + ret = __wait_on_bit_lock(page_waitqueue(page), &wait,
> sync_page_killable, TASK_KILLABLE);
> + /*
> + * wait_on_bit_lock uses prepare_to_wait_exclusive, so if multiple
> + * procs were waiting on this page, we were the only proc woken up.
> + *
> + * if ret != 0, we didn't actually get the lock. We need to
> + * make sure any other waiters don't sleep forever.
> + */
> + if (ret)
> + wake_up_page(page, PG_locked);
This patch assumes that nobody else calls __wait_on_bit_lock() with
action which can return !0. Currently this is correct, but perhaps
it makes sense to move this wake_up_page() into __wait_on_bit_lock ?
Note that we need to "transfer" the wakeup only if wake_up_page()
has already removed us from page_waitqueue(page), this means we
don't need to check ret != 0 twice in __wait_on_bit_lock(), afaics
we can do
if ((ret = (*action)(q->key.flags))) {
__wake_up_bit(wq, q->key.flags, q->key.bit_nr);
// or just __wake_up(wq, TASK_NORMAL, 1, &q->key);
break;
}
IOW, imho __wait_on_bit_lock() is buggy, not __lock_page_killable(),
no?
Oleg.
next reply other threads:[~2009-01-17 21:56 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-17 21:51 Oleg Nesterov [this message]
2009-01-18 1:38 ` [PATCH v3] wait: prevent waiter starvation in __wait_on_bit_lock Johannes Weiner
2009-01-18 2:32 ` Oleg Nesterov
2009-01-20 20:31 ` Johannes Weiner
2009-01-21 14:36 ` Oleg Nesterov
2009-01-21 21:38 ` [RFC v4] " Johannes Weiner
2009-01-22 20:25 ` Oleg Nesterov
2009-01-23 0:26 ` Dmitry Adamushko
2009-01-23 0:47 ` Oleg Nesterov
2009-01-23 10:07 ` Dmitry Adamushko
2009-01-23 11:05 ` Oleg Nesterov
2009-01-23 12:36 ` Dmitry Adamushko
2009-01-23 9:59 ` Johannes Weiner
2009-01-23 11:35 ` 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-27 3:23 ` Oleg Nesterov
2009-01-27 19:34 ` [RFC v6] " Johannes Weiner
2009-01-27 20:05 ` Oleg Nesterov
2009-01-27 22:31 ` Johannes Weiner
2009-01-28 9:14 ` [RFC v7] " Johannes Weiner
2009-01-29 4:42 ` Oleg Nesterov
2009-01-29 7:37 ` Andrew Morton
2009-01-29 8:31 ` Oleg Nesterov
2009-01-29 9:11 ` Andrew Morton
2009-01-29 14:34 ` Chris Mason
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
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=20090117215110.GA3300@redhat.com \
--to=oleg@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=cel@citi.umich.edu \
--cc=chris.mason@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=nickpiggin@yahoo.com.au \
/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