linux-kernel - Re: aranym bug, manifests as "ida_remove called for id=13" on recent kernels

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: <20101011043632.GA2566@cynthia.pants.nu>
Date:	Sun, 10 Oct 2010 21:36:32 -0700
From:	Brad Boyer <flar@...andria.com>
To:	Al Viro <viro@...IV.linux.org.uk>
Cc:	Geert Uytterhoeven <geert@...ux-m68k.org>,
	linux-m68k@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: aranym bug, manifests as "ida_remove called for id=13" on recent kernels

On Mon, Oct 11, 2010 at 03:41:03AM +0100, Al Viro wrote:
> Argh...  OK, going through aranym with debugger has exhonorated it.  My
> apologies ;-/  It *is* gcc in sid.  Testcase:
> 
> extern int foo(int);
> void *bar(int n)
> {
>         return (void *)foo(n);
> }
> 
> and gcc -S -O2 turns that into
> bar:
>         link.w %fp,#0
>         unlk %fp
>         jra foo
> 

I presume the bug is that foo put the return value in %d0 while bar
should have its return value in %a0. This function isn't eligible
for the optimization being used due to this need to move the result
into a different register.

> Spot the obvious bug...  BTW, why on the Earth does debian-ports m68k tree
> use gcc-4.3 with Cthulhu-scaring 700Kb gzipped patch and does *not* have
> gcc-4.4?

I believe that gcc-4.4 for m68k is being held up by the TLS support patches.
While I haven't been personally involved to any great degree, I got the
impression that the work is pretty much done other than getting it included.

	Brad Boyer
	flar@...andria.com

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