From: "David S. Miller" <davem@redhat.com>
To: ak@muc.de
Cc: zippel@linux-m68k.org, linux-kernel@vger.kernel.org
Subject: Re: __get_user usage in mm/slab.c
Date: Tue, 12 Mar 2002 07:25:31 -0800 (PST) [thread overview]
Message-ID: <20020312.072531.109169457.davem@redhat.com> (raw)
In-Reply-To: <20020312162316.A3505@averell>
In-Reply-To: <Pine.LNX.4.21.0203121237070.19747-100000@serv> <20020312162316.A3505@averell>
From: Andi Kleen <ak@muc.de>
Date: Tue, 12 Mar 2002 16:23:16 +0100
I guess set_fs(KERNEL_DS); __*_user() will not catch exceptions on m68k
currently, right?
I, for one, think it should.
next prev parent reply other threads:[~2002-03-12 15:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-12 11:58 __get_user usage in mm/slab.c Roman Zippel
2002-03-12 12:43 ` David S. Miller
2002-03-12 13:18 ` vinolin
2002-03-12 15:23 ` Andi Kleen
2002-03-12 15:25 ` David S. Miller [this message]
2002-03-12 16:32 ` Roman Zippel
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=20020312.072531.109169457.davem@redhat.com \
--to=davem@redhat.com \
--cc=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.org \
/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.