public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <srostedt@redhat.com>
To: Anders Kaseorg <andersk@ksplice.com>
Cc: Jason Baron <jbaron@redhat.com>,
	Masami Hiramatsu <mhiramat@redhat.com>,
	Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] jump label: Fix jump_label_text_reserved
Date: Thu, 28 Apr 2011 15:22:56 -0400	[thread overview]
Message-ID: <1304018576.4401.21.camel@fedora> (raw)
In-Reply-To: <BANLkTikG6atUB1mE8UF8Ew4ustb1gfFEjA@mail.gmail.com>

On Thu, 2011-04-28 at 15:10 -0400, Anders Kaseorg wrote:
> On Thu, Apr 28, 2011 at 14:42, Jason Baron <jbaron@redhat.com> wrote:
> > This is fixed in the jump label re-write patch, which is queued for
> > 2.6.40 in the -tip tree. See: http://marc.info/?l=linux-kernel&m=130391786701337&w=2
> 
> Okay.  It would be nice if the bug fixes had been separated out into

I didn't realize this was a bug fix that was noticed by current users,
otherwise I would have done so.

> commits that could be picked onto the -stable kernels.  Should I send
> my patch to stable@kernel.org?
> 
> > I believe only kprobes is relying on this check. Did you hit this in
> > practive using kprobes?
> 

If you do, note that it is pending in tip and give the commit id for it.
It will make stable as soon as the commit makes it in mainline in
the .40 merge window.

If possible we could cherry pick the patch for mainline to get it in
sooner, and it would just be a wash when it goes in with the current tip
branch.

-- Steve



      reply	other threads:[~2011-04-28 19:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-28 17:53 [PATCH] jump label: Fix jump_label_text_reserved Anders Kaseorg
2011-04-28 18:42 ` Jason Baron
2011-04-28 19:10   ` Anders Kaseorg
2011-04-28 19:22     ` 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=1304018576.4401.21.camel@fedora \
    --to=srostedt@redhat.com \
    --cc=andersk@ksplice.com \
    --cc=jbaron@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@redhat.com \
    --cc=mingo@elte.hu \
    /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