TWIMC: this mail is primarily send for documentation purposes and for regzbot, my Linux kernel regression tracking bot. These mails usually contain '#forregzbot' in the subject, to make them easy to spot and filter. On 13.09.22 17:37, Thorsten Leemhuis wrote: > > On 13.09.22 16:20, Peter Sutton wrote: >>> a fix for a deadlock for RFCOMM sk state change was posted last year already: >>> >>> https://lore.kernel.org/all/20211004180734.434511-1-desmondcheongzx@xxxxxxxxx/ >>> >>> It seems it never went anywhere, unless I'm missing something. Is that >>> maybe the same problem or somehow related? >> >> I mentioned this on the Arch Linux Matrix channel. The `linux` package >> maintainer said they had encountered the same and added the linked >> patch to the Arch Linux kernel package but removed it because it >> wasn't merged (which explains why my issue went way then came back). >> Anyway, we compiled a 5.19.8 `linux` package with the patch (which >> fixes my issue) and they said they'll add the patch back to the linux >> package. > > Well, that's fine and hopefully will solve your issue soon, but the arch > maintainers are right: this should be fixed upstream. > > Luiz, is there a reason why that patch wasn't merged? What is needed to > get this merged, ideally while adding a "Link: > https://lore.kernel.org/all/CAD+dNTsbuU4w+Y_P7o+VEN7BYCAbZuwZx2+tH+OTzCdcZF82YA@xxxxxxxxxxxxxx/"; > tag? #regzbot fixed-by: 812e92b824c1db16 Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) P.S.: As the Linux kernel's regression tracker I deal with a lot of reports and sometimes miss something important when writing mails like this. If that's the case here, don't hesitate to tell me in a public reply, it's in everyone's interest to set the public record straight.
