Hello, The original patch is already in linux-6.8.y, so I submitted the patch for the previous branches: - linux-6.2.y: https://lore.kernel.org/stable/20240815183641.7875-1-sergio.collado@xxxxxxxxx/T/#u - linux-6.4.y: https://lore.kernel.org/stable/20240815185026.8573-1-sergio.collado@xxxxxxxxx/T/#u - linux-6.5.y: https://lore.kernel.org/stable/20240815190146.9213-1-sergio.collado@xxxxxxxxx/T/#u - linux-6.6.y: https://lore.kernel.org/stable/20240815191047.9737-1-sergio.collado@xxxxxxxxx/T/#u I have not addressed the branches linux-6.3.y and linux-6.7.y as those are EOL: - https://lore.kernel.org/all/20230709111451.101012554@xxxxxxxxxxxxxxxxxxx/ - https://lore.kernel.org/all/20240401152553.125349965@xxxxxxxxxxxxxxxxxxx/ Please let me know if something is off. Sergio On Mon, 12 Aug 2024 at 16:37, Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > > On Tue, Jul 30, 2024 at 10:13:15PM +0200, Sergio González Collado wrote: > > From: Dave Kleikamp <dave.kleikamp@xxxxxxxxxx> > > > > [ Upstream commit a779ed754e52d582b8c0e17959df063108bd0656 ] > > > > In order to make array bounds checking sane, provide a separate > > definition of the in-inode xtree root and the external xtree page. > > > > Signed-off-by: Dave Kleikamp <dave.kleikamp@xxxxxxxxxx> > > Tested-by: Manas Ghandat <ghandatmanas@xxxxxxxxx> > > (cherry picked from commit a779ed754e52d582b8c0e17959df063108bd0656) > > Signed-off-by: Sergio González Collado <sergio.collado@xxxxxxxxx> > > Reported-by: syzbot+6b1d79dad6cc6b3eef41@xxxxxxxxxxxxxxxxxxxxxxxxx > > --- > > What about 6.6.y? We can't take commits only to older kernels, that > would mean you would have a regression. > > Please resubmit for all relevant branches. > > greg k-h
