linux-kernel - Re: SyS symbol munging.

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]

Message-ID: <20130510201743.GG22942@pd.tnic>
Date:	Fri, 10 May 2013 22:17:43 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	Al Viro <viro@...IV.linux.org.uk>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Dave Jones <davej@...hat.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: SyS symbol munging.

On Fri, May 10, 2013 at 09:05:03PM +0100, Al Viro wrote:
> Note that both sys_something and SyS_something end up in vmlinux
> symbol table, refering to the same address. AFAICS, what matters is
> which one goes first. May be even linker-dependent...

Interesting.

So it could be that a change in the linker may have caused the SyS
things to go first and start appearing in stack traces, not necessarily
a change in the kernel...

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--
--
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/