linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Sutton <peter@foxdogstudios.com>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: Paul Menzel <pmenzel@molgen.mpg.de>,
	Desmond Cheong Zhi Xi <desmondcheongzx@gmail.com>,
	Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
	linux-bluetooth@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: [Bug] [Deadlock] Kernel thread deadlock in rfcomm socket release when connect interrupted
Date: Tue, 13 Sep 2022 16:20:30 +0100	[thread overview]
Message-ID: <CAD+dNTsnVpyFKyZcAgnqAZz-e2upjFd3NGWV=hPhywL8k0g6Nw@mail.gmail.com> (raw)
In-Reply-To: <e7c8127a-d561-3a3d-f208-770f3abbee17@leemhuis.info>

>  a fix for a deadlock for RFCOMM sk state change was posted last year already:
>
> https://lore.kernel.org/all/20211004180734.434511-1-desmondcheongzx@gmail.com/
>
> 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.

  reply	other threads:[~2022-09-13 17:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-29 11:42 [Bug] [Deadlock] Kernel thread deadlock in rfcomm socket release when connect interrupted Peter Sutton
2022-05-30  7:22 ` Paul Menzel
2022-05-30 11:44   ` Peter Sutton
2022-09-11 15:42     ` Peter Sutton
2022-09-12  6:23       ` Paul Menzel
2022-09-13 15:06         ` Thorsten Leemhuis
2022-09-13 15:20           ` Peter Sutton [this message]
2022-09-13 15:33             ` Desmond Cheong Zhi Xi
2022-09-13 15:37             ` Thorsten Leemhuis
2022-09-27  9:34               ` [Bug] [Deadlock] Kernel thread deadlock in rfcomm socket release when connect interrupted #forregzbot Thorsten Leemhuis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAD+dNTsnVpyFKyZcAgnqAZz-e2upjFd3NGWV=hPhywL8k0g6Nw@mail.gmail.com' \
    --to=peter@foxdogstudios.com \
    --cc=desmondcheongzx@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=pmenzel@molgen.mpg.de \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).