From: Roman Zippel <zippel@linux-m68k.org>
To: Ken Ashcraft <kash@stanford.edu>
Cc: linux-kernel@vger.kernel.org, engler@stanford.edu
Subject: Re: null pointer questions
Date: Sat, 03 Nov 2001 00:20:44 +0100 [thread overview]
Message-ID: <3BE32A4C.9F9DBCC3@linux-m68k.org> (raw)
In-Reply-To: <Pine.GSO.4.33.0111021433590.6907-100000@saga18.Stanford.EDU>
Hi,
Ken Ashcraft wrote:
> Why does it matter if 0 is a valid user space or not? If I make the call
>
> copy_from_user(0, user_ptr, 4);
>
> the null pointer is the kernel address, not the user address. Can you
> clarify please?
Sorry, I misunderstood you. The kernel address has to be a valid address
of course, otherwise the behavior is undefined.
bye, Roman
next prev parent reply other threads:[~2001-11-02 23:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-02 7:30 Ken Ashcraft
2001-11-02 12:51 ` Roman Zippel
2001-11-02 13:16 ` lkml user
2001-11-02 22:42 ` Ken Ashcraft
2001-11-02 23:20 ` Roman Zippel [this message]
2001-11-02 23:37 ` Brian Gerst
2001-11-02 23:39 ` Brian Gerst
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=3BE32A4C.9F9DBCC3@linux-m68k.org \
--to=zippel@linux-m68k.org \
--cc=engler@stanford.edu \
--cc=kash@stanford.edu \
--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®