From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Brian Gerst <bgerst@didntduck.org>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] i386 __verify_write fixes
Date: 22 Oct 2002 16:06:18 +0100 [thread overview]
Message-ID: <1035299178.329.70.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <3DA9D3EF.9030000@quark.didntduck.org>
On Sun, 2002-10-13 at 21:13, Brian Gerst wrote:
> mark the page read-only. A 386 would continue to write to the page when
> the first thread woke up again. We need to prevent anyone from changing
> the page permissions until we are done writing to userspace. My
> suggestion is to replace access_ok() with begin_user_{read,write}(), and
> add end_user_{read,write}(). Thoughs?
For 2.6 with the time scale as it is I think we just block pre-emption
on 386. Its not a big deal since almost nobody uses 386 any more
prev parent reply other threads:[~2002-10-22 14:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-13 20:13 Brian Gerst
2002-10-22 15:06 ` Alan Cox [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=1035299178.329.70.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=bgerst@didntduck.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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 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®