From: Ingo Molnar <mingo@elte.hu>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>,
David Holmes - Sun Microsystems <David.Holmes@Sun.COM>,
Andrew Morton <akpm@linux-foundation.org>,
Stable Team <stable@kernel.org>
Subject: Re: [PATCH -v2] fix for futex_wait signal stack corruption
Date: Wed, 5 Dec 2007 11:31:11 +0100 [thread overview]
Message-ID: <20071205103111.GD22792@elte.hu> (raw)
In-Reply-To: <alpine.LFD.0.99999.0712050643440.3327@localhost.localdomain>
* Thomas Gleixner <tglx@linutronix.de> wrote:
> Just a minor nit. Can we please use "futex" instead of "fu" ? I'm just
> envisioning the next union member named "ba".
>
> Acked-by: Thomas Gleixner <tglx@linutronix.de>
>
> Please apply with the s/fu/futex/ change. This needs to go into stable
> .22/.23 as well.
ok, i've tied it all up, collected the Acks and will push Steve's fix to
Linus via the scheduler git tree - is that fine with everyone? I think
there's enough time to get this tested - Linus's latest tree shows up in
Fedora rawhide in 1-2 days and tons of apps use futexes.
Ingo
prev parent reply other threads:[~2007-12-05 10:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-04 20:57 [PATCH] fix for futex_wait signal stack corruption Steven Rostedt
2007-12-04 21:09 ` Linus Torvalds
2007-12-04 21:39 ` Steven Rostedt
2007-12-04 22:43 ` Linus Torvalds
2007-12-05 1:23 ` Steven Rostedt
2007-12-05 1:46 ` Linus Torvalds
2007-12-05 3:17 ` [PATCH -v2] " Steven Rostedt
2007-12-05 3:41 ` Linus Torvalds
2007-12-05 3:47 ` Randy Dunlap
2007-12-05 3:53 ` Steven Rostedt
2007-12-05 5:33 ` David Holmes - Sun Microsystems
2007-12-05 6:06 ` Linus Torvalds
2007-12-05 6:14 ` David Holmes - Sun Microsystems
2007-12-05 5:54 ` Thomas Gleixner
2007-12-05 10:31 ` Ingo Molnar [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=20071205103111.GD22792@elte.hu \
--to=mingo@elte.hu \
--cc=David.Holmes@Sun.COM \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=stable@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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.