[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAG48ez03UYAdqZcQxG9ejJFnSNE=ADU=mn-_zk9fmyBzTHo7QA@mail.gmail.com>
Date: Tue, 2 Sep 2025 18:13:24 +0200
From: Jann Horn <jannh@...gle.com>
To: Giovanni Cabiddu <giovanni.cabiddu@...el.com>
Cc: Rik van Riel <riel@...riel.com>, x86@...nel.org, linux-kernel@...r.kernel.org,
bp@...en8.de, peterz@...radead.org, dave.hansen@...ux.intel.com,
zhengqi.arch@...edance.com, nadav.amit@...il.com, thomas.lendacky@....com,
kernel-team@...a.com, linux-mm@...ck.org, akpm@...ux-foundation.org,
jackmanb@...gle.com, mhklinux@...look.com, andrew.cooper3@...rix.com,
Manali.Shukla@....com, mingo@...nel.org, Dave Hansen <dave.hansen@...el.com>,
baolu.lu@...el.com, david.guckian@...el.com, damian.muszynski@...el.com
Subject: Re: [BUG] x86/mm: regression after 4a02ed8e1cc3
On Tue, Sep 2, 2025 at 6:05 PM Jann Horn <jannh@...gle.com> wrote:
> To me this looks like a change that is correct but makes it easier to
> hit IOMMU flushing issues in other places.
(This was ambigous; to be clear, I meant that 4a02ed8e1cc3 looks
correct to me, and that the suggested fix doesn't look to me like it
fixes anything.)
Powered by blists - more mailing lists