From: Ralf Baechle <ralf@linux-mips.org>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: linux-mips@linux-mips.org
Subject: Re: [MIPS] Fix aliasing bug in copy_user_highpage, take 2.
Date: Mon, 15 Oct 2007 19:28:11 +0100 [thread overview]
Message-ID: <20071015182811.GA20157@linux-mips.org> (raw)
In-Reply-To: <20071016.023125.59033711.anemo@mba.ocn.ne.jp>
On Tue, Oct 16, 2007 at 02:31:25AM +0900, Atsushi Nemoto wrote:
> On Mon, 15 Oct 2007 16:47:30 +0100, linux-mips@linux-mips.org wrote:
> > Turns out 6a36458d9348265327d074bdd40bfb1c5b6fb2cb wasn't quite right.
> > When called for a page that isn't marked dirty it would artificially
> > create an alias instead of doing the obvious thing and access the page
> > via KSEG0.
> >
> > The same issue also exists in copy_to_user_page and copy_from_user_page
> > which was causing the machine to die under rare circumstances for example
> > when running ps if the BUG_ON() assertion added by the earlier fix was
> > getting triggered.
>
> This commit added a SetPageDcacheDirty() call for both
> copy_to_user_page() and copy_from_user_page(). The call in
> copy_from_user_page() is really needed?
After copy_from_user_page the page will reside in the D-cache. So just
in case it ever gets mapped to userspace and modified there we better
make sure its kernel address will get flushed before mapping it to user
space. If not, we might see stale data if the page got modified under
its userspace address.
Ralf
next prev parent reply other threads:[~2007-10-15 18:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <S20036863AbXJOPrf/20071015154735Z+80955@ftp.linux-mips.org>
2007-10-15 17:31 ` [MIPS] Fix aliasing bug in copy_user_highpage, take 2 Atsushi Nemoto
2007-10-15 18:28 ` Ralf Baechle [this message]
2007-10-16 15:29 ` Atsushi Nemoto
2007-10-16 15:38 ` Ralf Baechle
2007-10-16 16:13 ` Atsushi Nemoto
2007-10-16 16:16 ` Ralf Baechle
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=20071015182811.GA20157@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=anemo@mba.ocn.ne.jp \
--cc=linux-mips@linux-mips.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.