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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090605222650.GM29008@uranus.ravnborg.org>
Date:	Sat, 6 Jun 2009 00:26:50 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	"H. Peter Anvin" <hpa@...ux.intel.com>
Cc:	LKML <linux-kernel@...r.kernel.org>, linux-arch@...r.kernel.org
Subject: Re: "N" symbols and System.map

On Fri, May 01, 2009 at 03:24:18PM -0700, H. Peter Anvin wrote:
> Hi all,
> 
> right now, we filter out symbols that nm tag N, meaning "debugging 
> symbols", from System.map.  However, at least on x86, the 
> linker-generated symbol _end is tagged N, and in fact is the only N in 
> the entire image.
> 
> Are there other architectures which would suffer if N were included in 
> System.map, or would that be a reasonable thing to do?

Peter - what is status here?

Do you see _end tagged N with -tip?
We landed a lot of changes to vmlinux.lds there.

Needless to say I have not included N symbols for now.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ