public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Simon Baatz <gmbnomis@gmail.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Helge Deller <deller@gmx.de>, Benjamin LaHaise <bcrl@kvack.org>,
	linux-aio@kvack.org, linux-kernel@vger.kernel.org,
	linux-parisc@vger.kernel.org
Subject: Re: [PATCH] aio: fix D-cache aliasing issues
Date: Sat, 16 Nov 2013 21:07:18 +0100	[thread overview]
Message-ID: <20131116200717.GA18939@schnuecks.de> (raw)
In-Reply-To: <1384555325.2003.39.camel@dabdike.int.hansenpartnership.com>

On Fri, Nov 15, 2013 at 02:42:05PM -0800, James Bottomley wrote:
> On Fri, 2013-11-15 at 23:05 +0100, Helge Deller wrote:
> > When a user page mapping is released via kunmap*() functions, the D-cache needs
> > to be flushed via flush_dcache_page() to avoid D-cache aliasing issues.
> > 
> > This patch fixes aio on the parisc platform (and probably others).
> 
> This should be flush_kernel_dcache_page().  flush_dcache_page() is for
> full coherency but for unmap, we know the page was coherent going in and
> may have been modified by the kernel, so only the kernel view needs to
> be sync'd.  Technically, by the kernel API, the flush should be done
> *before* unmapping.  This would have mattered on parisc until we did
> flush via tmpalias which means we no-longer care if the mapping for the
> flush exists or not because we always recreate it via the tmpalias
> pages.

On ARM, flush_kernel_dcache_page() actually assumes that the page is
mapped.  It avoids double flushing of highmem pages by not flushing
in those cases where kunmap_atomic() already takes care of flushing.


- Simon

  reply	other threads:[~2013-11-16 20:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-15 22:05 [PATCH] aio: fix D-cache aliasing issues Helge Deller
2013-11-15 22:42 ` James Bottomley
2013-11-16 20:07   ` Simon Baatz [this message]
2013-11-16 20:09     ` Benjamin LaHaise
2013-11-17 21:23       ` Helge Deller
2013-11-17 21:49         ` James Bottomley
2013-11-17 23:47           ` Helge Deller
2013-11-18  0:52             ` James Bottomley
2013-11-18  1:15               ` John David Anglin
2013-11-18  1:50                 ` James Bottomley
2013-11-18  1:03             ` John David Anglin
2013-11-18 10:54         ` Simon Baatz
2013-11-18 11:24           ` Aw: " Helge Deller
2013-11-16 22:06     ` James Bottomley
2013-11-16 22:32       ` John David Anglin
2013-11-16 22:37         ` James Bottomley
2013-11-16 22:49           ` John David Anglin

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=20131116200717.GA18939@schnuecks.de \
    --to=gmbnomis@gmail.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=bcrl@kvack.org \
    --cc=deller@gmx.de \
    --cc=linux-aio@kvack.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-parisc@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