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:	Mon, 11 Oct 2010 15:24:28 +0100
From:	Al Viro <viro@...IV.linux.org.uk>
To:	Andreas Schwab <schwab@...ux-m68k.org>
Cc:	Thorsten Glaser <tg@...bsd.de>, linux-kernel@...r.kernel.org,
	linux-m68k@...r.kernel.org
Subject: Re: aranym bug, manifests as "ida_remove called for id=13" on recent
 kernels

On Mon, Oct 11, 2010 at 04:15:35PM +0200, Andreas Schwab wrote:
> Al Viro <viro@...IV.linux.org.uk> writes:
> 
> > Below is what I'm using on top of mainline kernel; it's a combination of
> > couple of patches in debian m68k kernel plus compile fixes.
> 
> Try Geert's linux-m68k tree.
> 
> > This kind of miscompile is definitely triggered in a lot of places -
> > anything that does return ERR_PTR(error) right after error = foo(...);
> > is going to get fscked and it's not a rare thing.
> 
> Only if they are optimized into tail calls.

And with -O2 4.3 does exactly that.

BTW, any comments on signal patchset?  Seems to work here, including the
stack expansion fixes, but that's on aranym.  I'll try to resurrect the
real hardware, but that may take a while.  If somebody could give it a beating
in the meanwhile...
--
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