From: David Howells <dhowells@redhat.com>
To: uClinux development list <uclinux-dev@uclinux.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [uClinux-dev] bug in order>0 page allocations with !CONFIG_MMU
Date: Fri, 05 Nov 2004 12:11:39 +0000 [thread overview]
Message-ID: <23098.1099656699@redhat.com> (raw)
In-Reply-To: <418B0C82.6060107@snapgear.com>
> > Why is doing this necessary at all? No one should be touching the
> > individual pages of a block allocation. The kernel should defend itself
> > against userspace trying to munmap part of a multipage mmap.
>
> I don't recall right now why we had to do this originally.
> It was absolutely neccessary once, but I don't think we need
> this anymore. At least it runs fine on m68knommu targets now
> without this.
I've just found out what it's necessary for. access_process_vm() as called
from, say, /proc/cmdline.
David
prev parent reply other threads:[~2004-11-05 12:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-04 14:28 bug in order>0 page allocations with !CONFIG_MMU David Howells
2004-11-05 5:15 ` [uClinux-dev] " Greg Ungerer
2004-11-05 12:11 ` David Howells [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=23098.1099656699@redhat.com \
--to=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=uclinux-dev@uclinux.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.