From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Oleg Nesterov <oleg@redhat.com>,
Al Viro <viro@zeniv.linux.org.uk>,
David Smith <dsmith@redhat.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Igor Zhbanov <i.zhbanov@samsung.com>,
Christoph Hellwig <hch@infradead.org>,
Paul Menage <menage@google.com>
Subject: Re: [RFC][PATCH] exec: Fix use after free of tracepoint trace_sched_process_exec
Date: Tue, 4 Feb 2014 15:31:28 -0500 [thread overview]
Message-ID: <20140204153128.4eb52cbc@gandalf.local.home> (raw)
In-Reply-To: <CA+55aFyObrVGXqncNboMzybeevPBOtAUcn-zur_B26VHJ1CEcg@mail.gmail.com>
On Tue, 4 Feb 2014 12:18:53 -0800
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> We do have bprm->file, and we could get a path from that. It would be
> more expensive, but for tracing execve that might be fine. Yes/no?
I actually looked at that. But it may duplicate a bit of code. I was
thinking perhaps of making helper functions to extract the path string
from the file pointer (if there isn't one already that I'm unaware of)
and using that. Also it might be used for places like proc.
-- Steve
next prev parent reply other threads:[~2014-02-04 20:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 17:05 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 [this message]
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
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=20140204153128.4eb52cbc@gandalf.local.home \
--to=rostedt@goodmis.org \
--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=menage@google.com \
--cc=oleg@redhat.com \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®