From: Greg KH <gregkh@linuxfoundation.org>
To: "Deucher, Alexander" <Alexander.Deucher@amd.com>
Cc: "Limonciello, Mario" <Mario.Limonciello@amd.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"mjanes@netflix.com" <mjanes@netflix.com>
Subject: Re: [6.18.y] Missing TLB fix for 6.18.y
Date: Fri, 15 May 2026 11:23:52 +0200 [thread overview]
Message-ID: <2026051544-slick-reconvene-a4de@gregkh> (raw)
In-Reply-To: <BL1PR12MB51440378065158CC8EE2E267F7392@BL1PR12MB5144.namprd12.prod.outlook.com>
On Tue, May 12, 2026 at 08:53:47PM +0000, Deucher, Alexander wrote:
> Public
>
> > -----Original Message-----
> > From: Greg KH <gregkh@linuxfoundation.org>
> > Sent: Tuesday, May 12, 2026 1:22 PM
> > To: Deucher, Alexander <Alexander.Deucher@amd.com>
> > Cc: Limonciello, Mario <Mario.Limonciello@amd.com>;
> > stable@vger.kernel.org; mjanes@netflix.com
> > Subject: Re: [6.18.y] Missing TLB fix for 6.18.y
> >
> > On Mon, May 04, 2026 at 07:52:21PM +0000, Deucher, Alexander wrote:
> > > Public
> > >
> > > > -----Original Message-----
> > > > From: Limonciello, Mario <Mario.Limonciello@amd.com>
> > > > Sent: Monday, May 4, 2026 3:43 PM
> > > > To: stable@vger.kernel.org
> > > > Cc: mjanes@netflix.com; Deucher, Alexander
> > > > <Alexander.Deucher@amd.com>
> > > > Subject: [6.18.y] Missing TLB fix for 6.18.y
> > > >
> > > > Hi,
> > > >
> > > > Mark Janes noticed that commit e9f58ff991dd4 ("drm/amdgpu: rework
> > > > how we handle TLB fences") was missing from 6.18.y.
> > > >
> > > > This went into 7.0-rc5 and was backported to 6.19.y but not 6.18.y.
> > > >
> > > > This is because this was one of those cases that the "Fixed" commit
> > > > was in both 6.18 and 6.19.y as different hashes:
> > > >
> > > > b4a7f4e7ad2b120a94f3111f92a11520052c762d
> > > > f3854e04b708d73276c4488231a8bd66d30b4671
> > > >
> > > > So can you please backport e9f58ff991dd4 to 6.18.y?
> > >
> > > There are missing dependencies. Please cherry pick all of the following:
> > >
> > > f4db9913e4d3 ("drm/amdgpu: validate the flush_gpu_tlb_pasid()")
> > > e3a6eff92bbd ("drm/amdgpu: Fix validating flush_gpu_tlb_pasid()")
> > > 9163fe4d790f ("Revert "drm/amdgpu: don't attach the tlb fence for
> > > SI"") 69c5fbd2b93b ("drm/amdgpu: rework how we handle TLB fences")
> >
> > In what order please? Can someone provide a list of the full set?
>
>
> That is the full set. Please apply the following in descending order:
> commit f4db9913e4d3 ("drm/amdgpu: validate the flush_gpu_tlb_pasid()")
> commit e3a6eff92bbd ("drm/amdgpu: Fix validating flush_gpu_tlb_pasid()")
> commit 9163fe4d790f ("Revert "drm/amdgpu: don't attach the tlb fence for SI"")
> commit 69c5fbd2b93b ("drm/amdgpu: rework how we handle TLB fences")
All now queued up, thanks!
greg k-h
next prev parent reply other threads:[~2026-05-15 9:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 19:43 [6.18.y] Missing TLB fix for 6.18.y Mario Limonciello
2026-05-04 19:52 ` Deucher, Alexander
2026-05-12 17:21 ` Greg KH
2026-05-12 20:53 ` Deucher, Alexander
2026-05-15 9:23 ` Greg KH [this message]
2026-05-04 19:53 ` Mario Limonciello
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=2026051544-slick-reconvene-a4de@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Alexander.Deucher@amd.com \
--cc=Mario.Limonciello@amd.com \
--cc=mjanes@netflix.com \
--cc=stable@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