[PATCH v2 0/2] Fix mmap memory boundary calculation

Joonas Lahtinen joonas.lahtinen at linux.intel.com
Mon Aug 12 09:18:56 UTC 2024


Quoting Jann Horn (2024-08-09 18:40:45)
> On Fri, Aug 9, 2024 at 4:48 PM Jann Horn <jannh at google.com> wrote:
> > On Tue, Aug 6, 2024 at 2:08 PM Joonas Lahtinen
> > <joonas.lahtinen at linux.intel.com> wrote:
> > > Quoting Andi Shyti (2024-08-06 12:46:07)
> > > > Hi Greg,
> > > >
> > > > same question without the stable mailing list not to trigger the
> > > > automatic reply.
> > > >
> > > > > Andi Shyti (2):
> > > > >   drm/i915/gem: Adjust vma offset for framebuffer mmap offset
> > > > >   drm/i915/gem: Fix Virtual Memory mapping boundaries calculation
> > > >
> > > > I have forgotten to actually Cc the stable mailing list here.
> > > > These two patches need to be merged together even if only the
> > > > second patch has the "Fixes:" tag.
> > > >
> > > > I could have used the "Requires:" tag, but the commit id would
> > > > change in between merges and rebases.
> > >
> > > The patches were the top two in drm-intel-gt-next and committed
> > > only few hours ago so I fixed up the patches adding Cc: stable
> > > and Requires:
> >
> > I'm not very familiar with how the DRM trees work - shouldn't fixes in
> > i915 go on the separate drm-intel-fixes branch so that they don't have
> > to wait for a merge window?
> 
> Ah, nevermind, I see it is already in drm-intel-fixes. Sorry for the noise.

Yeah, the DRM subsystem has a rather specific process.

Jann, do you consider the fix released already now that it is in -rc3 or will
you start the 30 day count from when 6.11 gets released? I hope the latter,
but just want to make sure there are no surprises.

Regards, Joonas


More information about the Intel-gfx mailing list