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:	Tue, 19 May 2009 10:52:38 -0700 (PDT)
From:	Martin Knoblauch <spamtrap@...bisoft.de>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Matt Mackall <mpm@...enic.com>, Ingo Molnar <mingo@...e.hu>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Rgeression: 2.6.30-rc6-git3 build error - ICE from drivers/char/random.c


----- Original Message ----

> From: Linus Torvalds <torvalds@...ux-foundation.org>
> To: Martin Knoblauch <spamtrap@...bisoft.de>
> Cc: Matt Mackall <mpm@...enic.com>; Ingo Molnar <mingo@...e.hu>; Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
> Sent: Tuesday, May 19, 2009 5:09:40 PM
> Subject: Re: Rgeression: 2.6.30-rc6-git3 build error - ICE from drivers/char/random.c
> 
> 
> 
> On Tue, 19 May 2009, Martin Knoblauch wrote:
> > 
> >  With your patch, the problem still remains. Line 1685 is the end of the 
> patched routine now.
> 
> Ok, so can you do two other simple tests:
> 
> - just remove the  "+ (long)&ret" entirely.
> 
>    Now, usually gcc doesn't have issues with non-asm things, but that's an 
>    odd way of getting the current stack address by lookin gat the address 
>    of a variable that hasn't even been used, so maybe it triggers some 
>    untested codepath in gcc (and thus the bug).
> 

 Removing above fixes the ICE. It does so in both the original and the patched version. 

 Removing get_cycles() has no effect wrt. the ICE.

Cheers
Martin

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ