From: Oleg Nesterov <oleg@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [for-next-3.11][PATCH 0/5] tracing: Final fixes for the race between open event file and deleting event
Date: Fri, 2 Aug 2013 15:45:30 +0200 [thread overview]
Message-ID: <20130802134530.GA18839@redhat.com> (raw)
In-Reply-To: <20130802024924.999067099@goodmis.org>
On 08/01, Steven Rostedt wrote:
>
> Is all the races that we are aware of between accessing event files and
> deleting events covered by these patches? I think I have them all.
Yes, I believe this covers all problems we discussed. I am not aware
of any other problem in this area.
Oleg.
next prev parent reply other threads:[~2013-08-02 13:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-02 2:49 [for-next-3.11][PATCH 0/5] tracing: Final fixes for the race between open event file and deleting event Steven Rostedt
2013-08-02 2:49 ` [for-next-3.11][PATCH 1/5] debugfs: debugfs_remove_recursive() must not rely on list_empty(d_subdirs) Steven Rostedt
2013-08-02 2:49 ` [for-next-3.11][PATCH 2/5] tracing: trace_remove_event_call() should fail if call/file is in use Steven Rostedt
2013-08-02 2:49 ` [for-next-3.11][PATCH 3/5] tracing: Add comment to describe special break case in probe_remove_event_call() Steven Rostedt
2013-08-02 2:49 ` [for-next-3.11][PATCH 4/5] tracing/kprobes: Fail to unregister if probe event files are in use Steven Rostedt
2013-08-02 2:49 ` [for-next-3.11][PATCH 5/5] tracing/uprobes: " Steven Rostedt
2013-08-02 13:45 ` Oleg Nesterov [this message]
2013-08-02 14:04 ` [for-next-3.11][PATCH 0/5] tracing: Final fixes for the race between open event file and deleting event 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=20130802134530.GA18839@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.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.