From: Manfred Spraul <manfred@colorfullife.com>
To: Georg Nikodym <georgn@somanetworks.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: v2.4.19-rmk4 slab.c: /proc/slabinfo uses broken instead of slab labels
Date: Thu, 28 Nov 2002 23:34:20 +0100 [thread overview]
Message-ID: <3DE699EC.9060600@colorfullife.com> (raw)
>
>
>> 1. Is the ARM __get_user() broken?
>> 2. Could I be doing something else broken that is confusing __get_user()?
>> 3. What was/is the intent of the test? Or stated differently, why on earth
>> would cachep->name be a user address?
>
>
get_user is the standard test for bad pointers: If the pointer is bad,
then the exception handler will prevent an oops.
Could you backport the get_fs()/set_fs() calls around the get_user()
from 2.5? I assume that ARM needs it to distiguish between kernel and
user addresses.
On i386, it's possible to skip set_fs() and use __get_user() - but
that's i386 specific. For example the i386 oops code uses that.
--
Manfred
next reply other threads:[~2002-11-28 22:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-28 22:34 Manfred Spraul [this message]
2002-11-28 22:40 ` Russell King
2002-11-29 18:24 ` Manfred Spraul
2002-11-29 22:51 ` Russell King
2002-11-29 23:33 ` Manfred Spraul
-- strict thread matches above, loose matches on Subject: below --
2002-11-27 20:15 Georg Nikodym
2002-11-27 21:40 ` Georg Nikodym
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=3DE699EC.9060600@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=georgn@somanetworks.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®