On Mon, Aug 12, 2024 at 07:49:34PM +0200, Salvatore Bonaccorso wrote: > Hi Greg, > > On Sun, Aug 11, 2024 at 05:40:58PM +0200, Greg Kroah-Hartman wrote: > > On Sun, Aug 11, 2024 at 05:03:45PM +0200, Salvatore Bonaccorso wrote: > > > Hi Greg, > > > > > > On Sun, Aug 11, 2024 at 12:09:30PM +0200, Greg Kroah-Hartman wrote: > > > > On Wed, Aug 07, 2024 at 10:35:11PM +0200, Salvatore Bonaccorso wrote: > > > > > Hi Greg, > > > > > > > > > > On Wed, Aug 07, 2024 at 04:59:39PM +0200, Greg Kroah-Hartman wrote: > > > > > > This is the start of the stable review cycle for the 6.1.104 release. > > > > > > There are 86 patches in this series, all will be posted as a response > > > > > > to this one. If anyone has any issues with these being applied, please > > > > > > let me know. > > > > > > > > > > > > Responses should be made by Fri, 09 Aug 2024 15:00:24 +0000. > > > > > > Anything received after that time might be too late. > > > > > > > > > > 6.1.103 had the regression of bpftool not building, due to a missing > > > > > backport: > > > > > > > > > > https://lore.kernel.org/stable/v8lqgl$15bq$1@xxxxxxxxxxxxx/ > > > > > > > > > > The problem is that da5f8fd1f0d3 ("bpftool: Mount bpffs when pinmaps > > > > > path not under the bpffs") was backported to 6.1.103 but there is no > > > > > defintion of create_and_mount_bpffs_dir(). > > > > > > > > > > it was suggested to revert the commit completely. > > > > > > > > Thanks for this, I'll fix it up after this release. > > > > > > Thanks! Note today Quentin Monnet proposed another solution by > > > cherry-picking two commits: > > > > > > https://lore.kernel.org/stable/67bfcb8a-e00e-47b2-afe2-970a60e4a173@xxxxxxxxxx/ > > > > They don't apply cleanly, so I'll just add a revert... > > FYI: Just realized that the breaking commit was as well queued for > older series 5.15.y, 5.10.y and 5.4.y, so that needs to be dropped > from those queues as well. Good catch, I'll go drop it now from them, thanks! greg k-h
