From: Richard Weinberger <richard@nod.at>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
Ley Foon Tan <lftan@altera.com>, Arnd Bergmann <arnd@arndb.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Daniel Walter <sahne@0x90.at>,
user-mode-linux-devel
<user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [BUG] uml panics with "Segfault with no mm" in v3.19-rc
Date: Wed, 10 Dec 2014 13:13:25 +0100 [thread overview]
Message-ID: <548838E5.8060701@nod.at> (raw)
In-Reply-To: <CAMuHMdUzc2=EodO5vxKVWdaDQeWXUM8w90ssQ4HvPyR6N-g8fA@mail.gmail.com>
Am 10.12.2014 um 12:59 schrieb Geert Uytterhoeven:
> On Wed, Dec 10, 2014 at 11:49 AM, Richard Weinberger <richard@nod.at> wrote:
>> Am 10.12.2014 um 11:46 schrieb Miklos Szeredi:
>>> The guilty commit is:
>>>
>>> 00f634bc522d "asm-generic: add generic futex for !CONFIG_SMP"
>>
>> Thanks a lot Miklos!
>> Your bisecting faster than I do.
>>
>> Let's dig into the issue!
>
> Do you need "select HAVE_FUTEX_CMPXCHG if FUTEX"?
> Cfr. commit e571c58f313d35c5 ("m68k: Skip futex_atomic_cmpxchg_inatomic()
> test") and commit 03b8c7b623c80af2 ("futex: Allow architectures to skip
> futex_atomic_cmpxchg_inatomic() test").
Bingo!
If UML selects HAVE_FUTEX_CMPXCHG the code path I've described in my previous mail
is no longer taken and makes it work again.
I did only a small test but nothing exploded so far.
> BTW, I still think the real problem is the wrong address space, cfr.
> "[PATCH/RFC] futex: Switch to USER_DS for futex test"
> (http://www.spinics.net/lists/linux-m68k/msg06597.html), so you may also
> want to try that.
> However, that caused problems on s390, as it ran too early:
> http://permalink.gmane.org/gmane.linux.kernel.next/30165
Yeah, this would also make sense for UML.
Thanks,
//richard
prev parent reply other threads:[~2014-12-10 12:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 10:46 [BUG] uml panics with "Segfault with no mm" in v3.19-rc Miklos Szeredi
2014-12-10 10:49 ` Richard Weinberger
2014-12-10 11:03 ` Arnd Bergmann
2014-12-10 12:05 ` Richard Weinberger
2014-12-10 11:59 ` Geert Uytterhoeven
2014-12-10 12:13 ` Richard Weinberger [this message]
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=548838E5.8060701@nod.at \
--to=richard@nod.at \
--cc=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=lftan@altera.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=sahne@0x90.at \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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