linux-kernel - Re: [PATCH] Wrong symbol resolved for RIP on OOPS/BUG

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] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 07 Nov 2013 08:25:01 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Ingo Molnar <mingo@...nel.org>,
	Marek Majkowski <marek@...udflare.com>,
	Jiri Slaby <jslaby@...e.cz>
CC:	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>, x86@...nel.org,
	Rusty Russell <rusty@...tcorp.com.au>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Wrong symbol resolved for RIP on OOPS/BUG

On 11/06/2013 11:54 PM, Ingo Molnar wrote:
> 
> There's a recent commit from Jiri Slaby that I think tries to address the 
> same problem:
> 
>   8d4c812a3e5f x86/dumpstack: Fix printk_address for direct addresses
> 
> You can find it in the -tip tree:
> 
>   git remote add tip git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> 

The only difference seems to be in the handling of the "reliable" flag.

I am wondering if we shouldn't promote this patch to urgent/stable,
though, since misleading oops messages could be very disruptive.

	-hpa

--
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/