[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190918133949.GA20296@infradead.org>
Date: Wed, 18 Sep 2019 06:39:49 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Thomas Hellström (VMware)
<thomas_os@...pmail.org>
Cc: linux-kernel@...r.kernel.org, pv-drivers@...are.com,
linux-graphics-maintainer@...are.com, x86@...nel.org,
Dave Hansen <dave.hansen@...ux.intel.com>,
Andy Lutomirski <luto@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
"H. Peter Anvin" <hpa@...or.com>,
Christoph Hellwig <hch@...radead.org>,
Christian König <christian.koenig@....com>,
Marek Szyprowski <m.szyprowski@...sung.com>,
Tom Lendacky <thomas.lendacky@....com>
Subject: Re: [PATCH v3 0/2] Fix SEV user-space mapping of unencrypted
coherent memory
This looks sensibe to me. x86 folks let me know if you guys want
to pick this up or if I should take it.
On Tue, Sep 17, 2019 at 03:01:13PM +0200, Thomas Hellström (VMware) wrote:
> As far as I can tell there are no current users of dma_mmap_coherent() with
> SEV or SME encryption which means that there is no need to CC stable.
Note that the usbfs access really should use it, as the current version
is completely broken on non-coherent architectures. That already
triggered on x86 dma_mmap_coherent fix. So I'd actually like to see
a stable backport to avoid hitting surprises.
Powered by blists - more mailing lists