linux-kernel - Re: [git pull] sparseirq / irq updates for v2.6.29

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: <86802c440812281606o6e8fbde1ub2e5055f83fea47@mail.gmail.com>
Date:	Sun, 28 Dec 2008 16:06:09 -0800
From:	"Yinghai Lu" <yinghai@...nel.org>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	"Ingo Molnar" <mingo@...e.hu>,
	"Linus Torvalds" <torvalds@...ux-foundation.org>,
	"KOSAKI Motohiro" <kosaki.motohiro@...il.com>,
	linux-kernel@...r.kernel.org,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Thomas Gleixner" <tglx@...utronix.de>,
	"Jesse Barnes" <jbarnes@...tuousgeek.org>,
	"Kamalesh Babulal" <kamalesh@...ux.vnet.ibm.com>
Subject: Re: [git pull] sparseirq / irq updates for v2.6.29

On Sun, Dec 28, 2008 at 3:55 PM, H. Peter Anvin <hpa@...or.com> wrote:
> Ingo Molnar wrote:
>>
>> ok, agreed. I was hoping for some more generic workaround but nothing
>> seemed to keep gcc from inlining such functions.
>>
>
> Other than blacklisting those gcc versions.  It's pretty easy to
> understand how a bug like that could creep in, since one of the main
> improvements of the early gcc4 series was better inlining as an
> optimization.

1. one time path add one dummy printk
2. multi path, could move it to another file.
could add one like kernel/weak.c to collect those ...

>
> --
> H. Peter Anvin, Intel Open Source Technology Center
> I work for Intel.  I don't speak on their behalf.

good to know.

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