linux-kernel - Re: [tip:x86/asmlinkage] lto: Make asmlinkage _

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:	Fri, 14 Feb 2014 06:38:23 -0800
From:	Andi Kleen <ak@...ux.intel.com>
To:	Borislav Petkov <bp@...en8.de>
Cc:	mingo@...nel.org, hpa@...or.com, linux-kernel@...r.kernel.org,
	tglx@...utronix.de, hpa@...ux.intel.com,
	linux-tip-commits@...r.kernel.org,
	Tim Chen <tim.c.chen@...ux.intel.com>
Subject: Re: [tip:x86/asmlinkage] lto: Make asmlinkage __visible

> I guess it is trying to tell me that static function pointers cannot be
> __visible:
> 
> static asmlinkage void (*sha256_transform_asm)(const char *, u32 *, u64);
> 
> and
> 
> static asmlinkage void (*sha512_transform_asm)(const char *, u64 *, u64);

Yes there are a couple such warnings now. static asmlinkage
does not make much sense. Can run a cocinelle rule over the tree
later, will send patches. 

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