linux-kernel - Re: [Bug #13185] New x86 warning

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: <200904261411.18097.rjw@sisk.pl>
Date:	Sun, 26 Apr 2009 14:11:17 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Kernel Testers List <kernel-testers@...r.kernel.org>,
	Andi Kleen <andi@...stfloor.org>, Jeff Garzik <jeff@...zik.org>
Subject: Re: [Bug #13185] New x86 warning

On Sunday 26 April 2009, Ingo Molnar wrote:
> 
> * Rafael J. Wysocki <rjw@...k.pl> wrote:
> 
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.29.  Please verify if it still should be listed and let me know
> > (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13185
> > Subject		: New x86 warning
> > Submitter	: Jeff Garzik <jeff@...zik.org>
> > Date		: 2009-04-22 6:46 (4 days old)
> > References	: http://marc.info/?l=linux-kernel&m=124038280020950&w=4
> 
> I saw this warning with certain GCC versions for several kernel 
> cycles, so it's not any recent change that triggers this and it is 
> not a regression.
> 
> GCC is simply wrong here - i have posted a workaround for that but 
> it is too ugly to be merged upstream.
> 
> > Handled-By	: Andi Kleen <andi@...stfloor.org>
> > Patch		: http://patchwork.kernel.org/patch/19330/
> > 		  http://patchwork.kernel.org/patch/19406/
> 
> This patch regresses on older GCC versions and doesnt really address 
> the GCC false positive warning either, it just removes the inline 
> function that triggers the warning.

OK, so this is not a kernel bug in fact.  I'm going to close it.

Thanks,
Rafael
--
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/