linux-kernel - Re: STT_FUNC for assembler checksum and semaphore ops

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]

Date:	Mon, 7 Jan 2008 20:22:59 +0100
From:	Sam Ravnborg <sam@...nborg.org>
To:	John Reiser <jreiser@...Wagon.com>
Cc:	Paul Mackerras <paulus@...ba.org>,
	Hirokazu Takata <takata@...ux-m32r.org>,
	"David S. Miller" <davem@...emloft.net>,
	Geert Uytterhoeven <geert@...ux-m68k.org>,
	Roman Zippel <zippel@...ux-m68k.org>,
	Greg Ungerer <gerg@...inux.org>,
	Mikael Starvik <starvik@...s.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org
Subject: Re: STT_FUNC for assembler checksum and semaphore ops

On Mon, Jan 07, 2008 at 09:23:37AM -0800, John Reiser wrote:
> Dear $ARCH Maintainers,
> 
> This patch adds Elf32_Sym .st_info (STT_FUNC) and .st_size for hand-coded
> checksum and semaphore subroutines.  I needed this info when writing a
> static analyzer for stack depth [grovel over ./vmlinux] on the um
> (UserModeLinux) $ARCH for i386.  The changes work on i386.  Other $ARCH
> are analogous but not tested.  Other arch/x86/lib/*.S are not used by um
> currently.  [Should analogous changes be made anyway?]
> 
> Comments?

I do not know the assembly stuff in question,
but the code you add would be nicer if packed in a macro.
You may even use _GLOBAL and/or ENTRY for your purpose.

	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/