On Thu, Jul 05, 2012 at 01:37:46PM +0100, Hillf Danton wrote: > On Wed, Jul 4, 2012 at 10:32 PM, Will Deacon <will.deacon@xxxxxxx> wrote: > > When allocating and returning clear huge pages to userspace as a > > response to a fault, we may zero and return a mapping to a previously > > dirtied physical region (for example, it may have been written by > > a private mapping which was freed as a result of an ftruncate on the > > backing file). On architectures with Harvard caches, this can lead to > > I/D inconsistency since the zeroed view may not be visible to the > > instruction stream. > > > > This patch solves the problem by flushing the region after allocating > > and clearing a new huge page. Note that PowerPC avoids this issue by > > performing the flushing in their clear_user_page implementation to keep > > the loader happy, however this is closely tied to the semantics of the > > PG_arch_1 page flag which is architecture-specific. > > > > Acked-by: Catalin Marinas <catalin.marinas@xxxxxxx> > > Signed-off-by: Will Deacon <will.deacon@xxxxxxx> > > --- > > Thanks:) > > Acked-by: Hillf Danton <dhillf@xxxxxxxxx> Thanks Hillf. Which tree does this stuff usually go through? Will -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx"> email@xxxxxxxxx </a>