linux-kernel - Re: [PATCH] jump label: Fix jump_label_text

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 28 Apr 2011 15:22:56 -0400
From:	Steven Rostedt <srostedt@...hat.com>
To:	Anders Kaseorg <andersk@...lice.com>
Cc:	Jason Baron <jbaron@...hat.com>,
	Masami Hiramatsu <mhiramat@...hat.com>,
	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] jump label: Fix jump_label_text_reserved

On Thu, 2011-04-28 at 15:10 -0400, Anders Kaseorg wrote:
> On Thu, Apr 28, 2011 at 14:42, Jason Baron <jbaron@...hat.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@...nel.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


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/