From: Peter Zijlstra <peterz@infradead.org>
To: Darren Hart <dvhltc@us.ibm.com>
Cc: "lkml," <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@elte.hu>,
John Kacur <jkacur@redhat.com>,
Eric Dumazet <eric.dumazet@gmail.com>,
Dinakar Guniguntala <dino@in.ibm.com>,
John Stultz <johnstul@linux.vnet.ibm.com>
Subject: Re: [PATCH V2] futex: Fix handling of bad requeue syscall pairing
Date: Mon, 10 Aug 2009 17:27:44 +0200 [thread overview]
Message-ID: <1249918064.17467.143.camel@twins> (raw)
In-Reply-To: <4A7CA8C0.7010809@us.ibm.com>
On Fri, 2009-08-07 at 15:20 -0700, Darren Hart wrote:
> From: Darren Hart <dvhltc@us.ibm.com>
>
> If futex_requeue(requeue_pi=1) finds a futex_q that was created by a call
> other the futex_wait_requeue_pi(), the q.rt_waiter may be null. If so,
> this will result in an oops from the following call graph:
>
> futex_requeue()
> rt_mutex_start_proxy_lock()
> task_blocks_on_rt_mutex()
> waiter->task dereference
> OOPS
>
> We currently WARN_ON() if this is detected, clearly this is inadequate.
> If we detect a mispairing in futex_requeue(), bail out, seding -EINVAL to
> user-space.
>
> V2: Fix parenthesis warnings.
>
> Signed-off-by: Darren Hart <dvhltc@us.ibm.com>
> Cc: Thomas Gleixner <tglx@linutronix.de>
Acked-by: Peter Zijlstra <peterz@infradead.org>
> Cc: Steven Rostedt <rostedt@goodmis.org>
> Cc: Ingo Molnar <mingo@elte.hu>
> CC: Eric Dumazet <eric.dumazet@gmail.com>
> CC: Dinakar Guniguntala <dino@in.ibm.com>
> CC: John Stultz <johnstul@us.ibm.com>
> ---
>
> kernel/futex.c | 11 +++++++++--
> 1 files changed, 9 insertions(+), 2 deletions(-)
>
>
> diff --git a/kernel/futex.c b/kernel/futex.c
> index df30983..4705d89 100644
> --- a/kernel/futex.c
> +++ b/kernel/futex.c
> @@ -1306,8 +1306,15 @@ retry_private:
> if (!match_futex(&this->key, &key1))
> continue;
>
> - WARN_ON(!requeue_pi && this->rt_waiter);
> - WARN_ON(requeue_pi && !this->rt_waiter);
> + /*
> + * FUTEX_WAIT_REQEUE_PI and FUTEX_CMP_REQUEUE_PI should always
> + * be paired with each other and no other futex ops.
> + */
> + if ((requeue_pi && !this->rt_waiter) ||
> + (!requeue_pi && this->rt_waiter)) {
> + ret = -EINVAL;
> + break;
> + }
>
> /*
> * Wake nr_wake waiters. For requeue_pi, if we acquired the
prev parent reply other threads:[~2009-08-10 15:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-07 21:45 [PATCH] futex: Fix handling of bad requeue syscall pairing Darren Hart
2009-08-07 22:20 ` [PATCH V2] " Darren Hart
2009-08-10 15:27 ` Peter Zijlstra [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=1249918064.17467.143.camel@twins \
--to=peterz@infradead.org \
--cc=dino@in.ibm.com \
--cc=dvhltc@us.ibm.com \
--cc=eric.dumazet@gmail.com \
--cc=jkacur@redhat.com \
--cc=johnstul@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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).