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? Ciao, Thorsten
