[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y9LnAzUP2K/cmqa5@casper.infradead.org>
Date: Thu, 26 Jan 2023 20:48:03 +0000
From: Matthew Wilcox <willy@...radead.org>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: "Fabio M. De Francesco" <fmdefrancesco@...il.com>,
Ira Weiny <ira.weiny@...el.com>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
Alexander Potapenko <glider@...gle.com>,
Andrey Konovalov <andreyknvl@...il.com>,
Tony Luck <tony.luck@...el.com>,
Bagas Sanjaya <bagasdotme@...il.com>,
David Sterba <dsterba@...e.com>,
Kees Cook <keescook@...omium.org>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
Thomas Gleixner <tglx@...utronix.de>,
Al Viro <viro@...iv.linux.org.uk>, Helge Deller <deller@....de>
Subject: Re: [PATCH] mm/highmem: Align-down to page the address for
kunmap_flush_on_unmap()
On Thu, Jan 26, 2023 at 12:38:58PM -0800, Andrew Morton wrote:
> On Thu, 26 Jan 2023 15:33:46 +0100 "Fabio M. De Francesco" <fmdefrancesco@...il.com> wrote:
>
> > If ARCH_HAS_FLUSH_ON_KUNMAP is defined (PA-RISC case), __kunmap_local()
> > calls kunmap_flush_on_unmap(). The latter currently flushes the wrong
> > address (as confirmed by Matthew Wilcox and Helge Deller). Al Viro
> > proposed to call kunmap_flush_on_unmap() on an aligned-down to page
> > address in order to fix this issue. Consensus has been reached on this
> > solution.
>
> What are the user-visible runtime effects of this flaw?
The version of this patch I sent out includes this information,
as well as the missed alignment for kunmap_atomic().
Powered by blists - more mailing lists