All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
	Oleg Nesterov <oleg@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Dave Jones <davej@redhat.com>
Subject: Re: [GIT PULL] tracing: final fixes for events and some
Date: Mon, 5 Aug 2013 16:32:57 +0200	[thread overview]
Message-ID: <20130805143257.GA32639@gmail.com> (raw)
In-Reply-To: <1375712355.22073.45.camel@gandalf.local.home>


* Steven Rostedt <rostedt@goodmis.org> wrote:

> Linus,
> 
> Oleg Nesterov has been working hard in closing all the holes that can 
> lead to race conditions between deleting an event and accessing an event 
> debugfs file. This included a fix to the debugfs system (acked by Greg 
> Kroah-Hartman). We think that all the holes have been patched and 
> hopefully we don't find more. I haven't marked all of them for stable 
> because I need to examine them more to figure out how far back some of 
> the changes need to go.

Sigh, that's quite some churn still - unless these bugs were introduced in 
the v3.11 merge window (i.e. are genuine _regressions_), shouldn't such 
invasive fixes really go into v3.12 instead?

I see that some of the fixes here fix issues that your earlier post-rc1 
rounds of non-regression fixes introduced to begin with. That's really not 
a good pattern either IMO.

Thanks,

	Ingo

  reply	other threads:[~2013-08-05 14:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-05 14:19 [GIT PULL] tracing: final fixes for events and some Steven Rostedt
2013-08-05 14:32 ` Ingo Molnar [this message]
2013-08-05 14:52   ` Steven Rostedt
2013-08-12 18:13     ` Ingo Molnar
2013-08-13  2:39       ` Dave Jones
2013-08-13  3:14         ` Steven Rostedt
2013-08-13 11:06           ` Ingo Molnar
2013-08-13 11:45             ` Dave Jones
2013-08-13 14:01               ` 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=20130805143257.GA32639@gmail.com \
    --to=mingo@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=davej@redhat.com \
    --cc=fweisbec@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --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 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.