From: Chris Bainbridge <chris.bainbridge@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: linux-acpi@vger.kernel.org, lv.zheng@intel.com, mingo@redhat.com,
peterz@infradead.org, rjw@rjwysocki.net, oleg@redhat.com,
aystarik@gmail.com
Subject: Re: [PATCH] Preserve task state in reentrant calls to ___wait_event
Date: Sat, 7 Nov 2015 08:32:43 +0000 [thread overview]
Message-ID: <20151107083243.GA14648@localhost> (raw)
In-Reply-To: <20151106204408.GA11609@localhost>
On Fri, Nov 06, 2015 at 08:44:08PM +0000, Chris Bainbridge wrote:
> -#define ___wait_event(wq, condition, state, exclusive, ret, cmd) \
> +#define ___wait_event(wq, condition, nstate, exclusive, ret, cmd) \
> ({ \
> __label__ __out; \
> wait_queue_t __wait; \
> long __ret = ret; /* explicit shadow */ \
> + long ostate = current->state; \
XXX
> \
> INIT_LIST_HEAD(&__wait.task_list); \
> if (exclusive) \
> @@ -222,16 +223,16 @@ wait_queue_head_t *bit_waitqueue(void *, int);
> __wait.flags = 0; \
> \
> for (;;) { \
> - long __int = prepare_to_wait_event(&wq, &__wait, state);\
> + long __int = prepare_to_wait_event(&wq, &__wait, nstate);\
> \
> if (condition) \
> break; \
> \
> - if (___wait_is_interruptible(state) && __int) { \
> + if (___wait_is_interruptible(nstate) && __int) { \
> __ret = __int; \
> if (exclusive) { \
> abort_exclusive_wait(&wq, &__wait, \
> - state, NULL); \
> + nstate, NULL); \
> goto __out; \
> } \
> break; \
> @@ -240,6 +241,7 @@ wait_queue_head_t *bit_waitqueue(void *, int);
> cmd; \
> } \
> finish_wait(&wq, &__wait); \
> + set_current_state(ostate); \
I'm not convinced that this particular code is (or can be) race free in
the general reentrant case. The outer call to ___wait_event will miss
any wake_up received in the inner call between XXX above (store of
current->state) and this point of restoring the previous state. So if
the inner condition evaluation or some interrupt handler happens to
trigger a wake_up meant for the outer call then it will be lost.
> __out: __ret; \
> })
next prev parent reply other threads:[~2015-11-07 8:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 20:44 [PATCH] Preserve task state in reentrant calls to ___wait_event Chris Bainbridge
2015-11-06 23:06 ` Rafael J. Wysocki
2015-11-12 18:05 ` [PATCH] ACPI / SMBus: Fix boot stalls / high CPU caused by reentrant code Chris Bainbridge
2015-11-12 19:24 ` [PATCH] Revert "ACPI / SBS: Add 5 us delay to fix SBS hangs on MacBook" Chris Bainbridge
2015-11-07 8:32 ` Chris Bainbridge [this message]
2015-11-07 9:19 ` [PATCH] Preserve task state in reentrant calls to ___wait_event Peter Zijlstra
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=20151107083243.GA14648@localhost \
--to=chris.bainbridge@gmail.com \
--cc=aystarik@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lv.zheng@intel.com \
--cc=mingo@redhat.com \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=rjw@rjwysocki.net \
/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