On Monday, 27 March 2023 17:35:25 CEST Diederik de Haas wrote: > While looking into it, I did find some troubling aspects though. > I noticed that in upstream's master branch there were quite some commits > *after* 6.1 of which a reasonable amount has been backported to 6.1. > For example, in 6.1.21 there are FIVE commits which fix a memory leak. > > Those got backported because the original commits contained > "Fixes: <commit ID>" > > There are however also some commits which do NOT have the "Fixes:" tag, > like: > https://lore.kernel.org/all/20230228140835.4075-7-ranjan.kumar@broadcom.com > / titled: "mpi3mr: Bad drive in topology results kernel crash" > > There are some more and for that compare upstream's master branch with 6.1 > and look for the ones which do not have the "Fixes:" tag. > Unless explicit action is taken to request a backport, f.e. the above > mentioned commit will not get backported to 6.1 ... which could lead to a > kernel crash. I noticed that Salvatore responded to that thread and was a bit surprised that I didn't see a quick follow-up from that. But it looks like Sasha Levin has backported 4 out of 6 patches: https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/commit/queue-6.1?id=293e8033e127c25a74c680d61505f9f19b917ccf Normally they would be included in the 6.1.22 release.
Attachment:
signature.asc
Description: This is a digitally signed message part.