Hi Juergen, On 15/02/25 7:09 PM, Jürgen Groß wrote: > On 15.02.25 13:34, Greg KH wrote: >> On Sat, Feb 15, 2025 at 12:47:57PM +0100, Jürgen Groß wrote: >>> On 12.02.25 16:12, Harshit Mogalapalli wrote: >>>> Hi Salvatore, >>>> >>>> On 12/02/25 00:56, Salvatore Bonaccorso wrote: >>>>> Hi Harshit, >>>>> >>>>> On Sun, Feb 09, 2025 at 01:45:38AM +0530, Harshit Mogalapalli wrote: >>>>>> Hi Salvatore, >>>>>> >>>>>> On 08/02/25 21:26, Salvatore Bonaccorso wrote: >>>>>>> Hi Juergen, hi all, >>>>>>> >>>>>>> Radoslav Bodó reported in Debian an issue after updating our kernel >>>>>>> from 6.1.112 to 6.1.115. His report in full is at: >>>>>>> >>>>>>> https://bugs.debian.org/1088159 >>>>>>> >>>>>> >>>>>> Note: >>>>>> We have seen this on 5.4.y kernel: More details here: >>>>>> https://lore.kernel.org/all/9dd91f6e-1c66-4961-994e-dbda87d69dad@xxxxxxxxxx/ >>>>>> >>>>> >>>>> Thanks for the pointer, so looking at that thread I suspect the three >>>>> referenced bugs in Debian are in the end all releated. We have one as >>>>> well relating to the megasas_sas driver, this one for the mpt3sas >>>>> driver and one for the i40e driver). >>>>> >>>>> AFAICS, there is not yet a patch which has landed upstream which I >>>>> can >>>>> redirect to a affected user to test? >>>>> >>>> >>>> Konrad pointed me at this thread: https://lore.kernel.org/ >>>> all/20250211120432.29493-1-jgross@xxxxxxxx/ >>>> >>>> This has some fixes, but not landed upstream yet. >>> >>> Patches are upstream now. In case you still experience any problems, >>> please >>> speak up. >> >> What specific commits should be backported here? > > Those are: > > e93ec87286bd1fd30b7389e7a387cfb259f297e3 > 85fcb57c983f423180ba6ec5d0034242da05cc54 Is there a plan to backport a 5.4 variant of this series. I tried backporting it to 5.4 myself but found a lot of conflicts. It doesn't seem to be compliant with 5.4 swiotlib. If you could guide me as to how you would recommend backporting this for 5.4, whether it is via backporting multiple supporting patches to make the cherry-pick clean or manually resolving conflicts in the patch itself, that'll be highly appreciated. > > > Juergen > >> >> thanks, >> >> greg k-h > Thanks, Harshvardhan
