From: Andreas Schwab <schwab@linux-m68k.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Finn Thain <fthain@telegraphics.com.au>,
Linux/m68k <linux-m68k@vger.kernel.org>,
Mikael Pettersson <mikpelinux@gmail.com>
Subject: Re: Boot crash on 68030, was Re: [PATCH][M68K] implement futex.h to support userspace robust futexes and PI mutexes
Date: Tue, 10 Dec 2013 11:19:23 +0100 [thread overview]
Message-ID: <mvmy53t6mac.fsf@hawking.suse.de> (raw)
In-Reply-To: <CAMuHMdVB3w3JpNSrdZXPk+xrDXyhm-CgDHX5XW_1CUKn8pQmtA@mail.gmail.com> (Geert Uytterhoeven's message of "Tue, 10 Dec 2013 11:12:50 +0100")
Geert Uytterhoeven <geert@linux-m68k.org> writes:
>> Data read fault at 0x00000000 in Super Data (pc=0x3afec)
>> BAD KERNEL BUSERR
I think futex_init needs to do set_fs(USER_DS), since futex is about
user data.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2013-12-10 10:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-08 14:03 [PATCH][M68K] implement futex.h to support userspace robust futexes and PI mutexes Mikael Pettersson
2013-05-17 8:44 ` Andreas Schwab
2013-05-17 9:02 ` Geert Uytterhoeven
2013-05-17 9:38 ` Andreas Schwab
2013-05-17 10:04 ` Geert Uytterhoeven
2013-05-17 12:05 ` Mikael Pettersson
2013-05-31 9:16 ` Geert Uytterhoeven
2013-12-09 23:11 ` Boot crash on 68030, was " Finn Thain
2013-12-09 23:27 ` Andreas Schwab
2013-12-10 0:54 ` Finn Thain
2013-12-10 10:12 ` Geert Uytterhoeven
2013-12-10 10:19 ` Andreas Schwab [this message]
2014-02-28 3:12 ` futex_init() vs. KERNEL_DS, was Re: Boot crash on 68030 Finn Thain
2014-02-28 7:48 ` Heiko Carstens
2014-02-28 10:30 ` Finn Thain
2014-02-21 2:33 ` Boot crash on 68030, was Re: [PATCH][M68K] implement futex.h to support userspace robust futexes and PI mutexes Finn Thain
2014-02-21 9:53 ` Andreas Schwab
2013-12-10 10:13 ` Mikael Pettersson
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=mvmy53t6mac.fsf@hawking.suse.de \
--to=schwab@linux-m68k.org \
--cc=fthain@telegraphics.com.au \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=mikpelinux@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.