From: Greg KH <greg@kroah.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Greg KH <gregkh@suse.de>, Lai Jiangshan <laijs@cn.fujitsu.com>,
Johannes Berg <johannes@sipsolutions.net>,
LKML <linux-kernel@vger.kernel.org>, stable <stable@kernel.org>
Subject: Re: [stable] [PATCH for stable] tracing: Consolidate protection of reader access to the ring buffer
Date: Fri, 25 Jun 2010 15:54:10 -0700 [thread overview]
Message-ID: <20100625225410.GJ10683@kroah.com> (raw)
In-Reply-To: <1277213804.9181.30.camel@gandalf.stny.rr.com>
On Tue, Jun 22, 2010 at 09:36:44AM -0400, Steven Rostedt wrote:
> On Tue, 2010-06-22 at 06:28 -0700, Greg KH wrote:
> > On Tue, Jun 22, 2010 at 09:23:03AM -0400, Steven Rostedt wrote:
> > > Greg,
> > >
> > > Johannes has been hitting a bug in 2.6.33 that we believe is fixed with
> > > the following patch. The bug is hit a few times a week, so it is hard to
> > > verify. But we are only hitting it with .33 and not .34, and this patch
> > > looks like it would be the one to fix it.
> > >
> > > Can you apply this patch to the 2.6.33 stable series.
> >
> > If you are ok with it, I'll apply it as it does look a little "big" for
> > a stable kernel :)
>
> Yeah, I usually would not ask for a patch this size to go into stable,
> but it has been in mainline for a while, and seems to be the fix for a
> bug we are hitting in .33.
Ok, all queued up now.
greg k-h
prev parent reply other threads:[~2010-06-25 23:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 13:23 [PATCH for stable] tracing: Consolidate protection of reader access to the ring buffer Steven Rostedt
2010-06-22 13:28 ` Greg KH
2010-06-22 13:36 ` Steven Rostedt
2010-06-25 22:54 ` Greg KH [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=20100625225410.GJ10683@kroah.com \
--to=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=johannes@sipsolutions.net \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=stable@kernel.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.