linux-kernel - Re: [PATCH] lto, watchdog/hpwdt.c: Make assembler label global

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: <20130806135118.aa11129d582b8aee00accb8a@linux-foundation.org>
Date:	Tue, 6 Aug 2013 13:51:18 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	linux-kernel@...r.kernel.org, Andi Kleen <ak@...ux.intel.com>,
	wim@...ana.be
Subject: Re: [PATCH] lto, watchdog/hpwdt.c: Make assembler label global

On Mon,  5 Aug 2013 15:16:39 -0700 Andi Kleen <andi@...stfloor.org> wrote:

> We cannot assume that the inline assembler code always ends up
> in the same file as the original C file.

um, why not?  You put an asm(".text\n...") into a .c file and you
expect that assembly code to be emitted into the .s file then assembled
into the .o file.

Obviously something somewhere is doing something unexpected.  Much more
detail needed, please.

Also...  what's "lto"?  Link Time Optimization?  It's unclear how this
fits into that.  Please provide that additional background info in these
patches so that others know what's going on and so that others (such as
me) can help people avoid making these mistakes in the future.

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