From: Al Viro <viro@ZenIV.linux.org.uk>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Thorsten Glaser <tg@mirbsd.de>,
linux-kernel@vger.kernel.org, linux-m68k@vger.kernel.org
Subject: Re: aranym bug, manifests as "ida_remove called for id=13" on recent kernels
Date: Mon, 11 Oct 2010 15:24:28 +0100 [thread overview]
Message-ID: <20101011142428.GK19804@ZenIV.linux.org.uk> (raw)
In-Reply-To: <m3wrpo24u0.fsf@hase.home>
On Mon, Oct 11, 2010 at 04:15:35PM +0200, Andreas Schwab wrote:
> Al Viro <viro@ZenIV.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...
next prev parent reply other threads:[~2010-10-11 14:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 17:49 aranym bug, manifests as "ida_remove called for id=13" on recent kernels Al Viro
2010-10-10 9:47 ` Geert Uytterhoeven
2010-10-10 14:49 ` Al Viro
2010-10-10 20:18 ` Geert Uytterhoeven
2010-10-10 23:52 ` Al Viro
2010-10-11 2:41 ` Al Viro
2010-10-11 4:36 ` Brad Boyer
2010-10-11 4:48 ` Al Viro
2010-10-11 12:21 ` Thorsten Glaser
2010-10-11 13:10 ` Andreas Schwab
2010-10-11 13:35 ` Al Viro
2010-10-11 14:15 ` Andreas Schwab
2010-10-11 14:24 ` Al Viro [this message]
2010-10-11 22:02 ` Al Viro
2010-11-02 15:30 ` Geert Uytterhoeven
2010-10-11 19:05 ` Mikael Pettersson
2010-10-11 9:27 ` Mikael Pettersson
2010-10-11 11:50 ` Mikael Pettersson
2010-10-11 12:29 ` Andreas Schwab
2010-10-11 8:39 ` Geert Uytterhoeven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101011142428.GK19804@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=schwab@linux-m68k.org \
--cc=tg@mirbsd.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox