From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Oleg Nesterov <oleg@redhat.com>, David Smith <dsmith@redhat.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Igor Zhbanov <i.zhbanov@samsung.com>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [RFC][PATCH] exec: Fix use after free of tracepoint trace_sched_process_exec
Date: Wed, 5 Feb 2014 01:10:29 +0000 [thread overview]
Message-ID: <20140205011028.GM10323@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CA+55aFyTC1UGvRgH5vASh-C3M+GqHPMNGsUq3Q1MuynzkiSaEA@mail.gmail.com>
On Tue, Feb 04, 2014 at 04:57:31PM -0800, Linus Torvalds wrote:
> On Tue, Feb 4, 2014 at 3:42 PM, Steven Rostedt <rostedt@goodmis.org> wrote:
> >
> > New version that moves all the ugliness into a static inline helper
> > function.
>
> Ok, that's better, but I really think we should just use "getname()"
> and "putname()".
Umm... Interactions with aushit might be interesting. It hooks into
getname() and putname(); I'm not up to doing analysis right now (13 hours
of nearly non-stop {R,Grep}TFS today already and I'm ears-deep in
looking through locking implications of Miklos' stuff at the moment ;-/),
but it's worth looking into; there may be dragons.
next prev parent reply other threads:[~2014-02-05 1:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 17:05 [RFC][PATCH] exec: Fix use after free of tracepoint trace_sched_process_exec Steven Rostedt
2014-02-04 19:00 ` Oleg Nesterov
2014-02-04 20:10 ` Steven Rostedt
2014-02-04 20:18 ` Linus Torvalds
2014-02-04 20:31 ` Steven Rostedt
2014-02-04 23:28 ` Steven Rostedt
2014-02-04 23:42 ` Steven Rostedt
2014-02-05 0:57 ` Linus Torvalds
2014-02-05 1:10 ` Al Viro [this message]
2014-02-05 3:37 ` Linus Torvalds
2014-02-05 13:52 ` Oleg Nesterov
2014-02-05 16:52 ` Linus Torvalds
2014-02-05 2:31 ` Steven Rostedt
2014-02-05 2:51 ` Steven Rostedt
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=20140205011028.GM10323@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=dsmith@redhat.com \
--cc=hch@infradead.org \
--cc=i.zhbanov@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=rostedt@goodmis.org \
--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