From: Randy Dunlap <randy.dunlap@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
David Holmes - Sun Microsystems <David.Holmes@Sun.COM>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH -v2] fix for futex_wait signal stack corruption
Date: Tue, 4 Dec 2007 19:47:19 -0800 [thread overview]
Message-ID: <20071204194719.e048ebc1.randy.dunlap@oracle.com> (raw)
In-Reply-To: <alpine.LFD.0.9999.0712041935140.13796@woody.linux-foundation.org>
On Tue, 4 Dec 2007 19:41:32 -0800 (PST) Linus Torvalds wrote:
>
> Patch looks fine to me.
>
> On Tue, 4 Dec 2007, Steven Rostedt wrote:
> >
> > Note: I'm a bit nervious to add "linux/types.h" and use u32 and u64
> > in thread_info.h, when there's a #ifdef __KERNEL__ just below that.
> > Not sure what that is there for.
>
> Hmm. I'd not expect user-mode headers to ever include
> <linux/thread-info.h>, and if they do, they'd already get get totally
> invalid namespace pollution ("struct restart_block" at a minimum) along
> with stuff that simply isn't sensible in user-space at all, so I think
> this part is fine.
>
> And I guess somebody will scream if it bites them ;)
>
> Anyway, my gut feel is that this is potentially a real problem, and we
> should fix it asap (ie it should go into 2.6.24 even at this late stage in
> the game), but it would be nice to know if the problem actually hit any
> actual real program, and not just a test-setup.
Steve/David,
where can I find the test case, please?
> So here's a question for David Holmes: What caused you to actually notice
> this behaviour? Can this actually be seen in real life usage?
>
> Anyway, at a minimum, here's an
>
> Acked-by: Linus Torvalds <torvalds@linux-foundation.org>
>
> and I suspect I should just apply it directly. Any comments from anybody
> else?
---
~Randy
Features and documentation: http://lwn.net/Articles/260136/
next prev parent reply other threads:[~2007-12-05 3:49 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 [this message]
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
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=20071204194719.e048ebc1.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=David.Holmes@Sun.COM \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox