mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Oleg Nesterov <oleg@redhat.com>
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, 02 Aug 2013 10:04:19 -0400	[thread overview]
Message-ID: <1375452259.22073.3.camel@gandalf.local.home> (raw)
In-Reply-To: <20130802134530.GA18839@redhat.com>

On Fri, 2013-08-02 at 15:45 +0200, Oleg Nesterov wrote:
> 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.

Great! I just pushed this to for-next. I'll let it sit there for over
the weekend, and if there's no more issues, I'll push this off to Linus.

Hopefully this will be the last of the changes needed for 3.11 :-)

I'll then need to look at all the changes made and put together a set of
changes to send to stable. I didn't mark any of these with stable as
there's lots of dependencies I need to figure out and some of these
fixes need to go back quite a ways.

Thanks for all your help (you and Masami :-)

-- Steve



      reply	other threads:[~2013-08-02 14:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-02  2:49 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 ` [for-next-3.11][PATCH 0/5] tracing: Final fixes for the race between open event file and deleting event Oleg Nesterov
2013-08-02 14:04   ` Steven Rostedt [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=1375452259.22073.3.camel@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=mingo@kernel.org \
    --cc=oleg@redhat.com \
    /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®