Re: [PATCH 5.10.y 0/4] Backport series: "permit write-sealed memfd read-only shared mappings"

[Isaac Manjarres <isaacmanjarres@google.com>]

On Thu, Jul 31, 2025 at 06:58:41AM +0200, Greg KH wrote:
> On Thu, Jul 31, 2025 at 05:40:29AM +0100, Lorenzo Stoakes wrote:
> > On Wed, Jul 30, 2025 at 03:26:01PM -0700, Isaac Manjarres wrote:
> > > On Wed, Jul 30, 2025 at 08:34:02PM +0100, Lorenzo Stoakes wrote:
> > > > > >
> > > > > > Having said that, I'm not against you doing this, just wondering about
> > > > > > that.
> > > > > >
> > > > > > Also - what kind of testing have you do on these series?
> > > > > I did the following tests:
> > > > >
> > > > > 1. I have a unit test that tries to map write-sealed memfds as
> > > > > read-only and shared. I verified that this works for each kernel version
> > > > > that this series is being applied to.
> > > > >
> > > > > 2. Android devices do use memfds as well, so I did try these patches out
> > > > > on a device running each kernel version, and tried boot testing, using
> > > > > several apps/games. I was looking for functional failures in these
> > > > > scenarios but didn't encounter any.
> > > > >
> > > > > Do you have any other recommendations of what I should test?
> > > >
> > > > No, that sounds good to me! Thank you for taking the time to implement and
> > > > carefully check this :)
> > > >
> > > > In this case I have no objections to these backports!
> > > >
> > > > Cheers, Lorenzo
> > >
> > > Thanks Lorenzo! Just to confirm, is there anything required from my
> > > end for these patches or they'll get reviewed and merged over time?
> > 
> > No, these should all be good to go, Greg + Sasha handle the stable kernels
> > and should percolate through their process (I see Sasha's scripts have been
> > firing off already :)
> 
> Yeah, give us a week or so to catch up with all of the recently
> submitted changes, the merge window, AND finally, a vacation for the
> stable maintainers....
> 

Understood. Thank you all for this!

--Isaac