Netdev List
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
	Karl Mehltretter <kmehltretter@gmail.com>,
	gregkh@linuxfoundation.org, luiz.dentz@gmail.com,
	luiz.von.dentz@intel.com, marcel@holtmann.org,
	johan.hedberg@gmail.com, eadavis@qq.com, davem@davemloft.net,
	kuba@kernel.org, linux-bluetooth@vger.kernel.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	patches@lists.linux.dev,
	syzbot+b7f6f8c9303466e16c8a@syzkaller.appspotmail.com
Subject: Re: [PATCH 5.10.y] Bluetooth: L2CAP: Fix deadlock
Date: Thu, 17 Sep 2026 20:52:35 -0400	[thread overview]
Message-ID: <2026-09-17-daily-reply-0008-l2cap-deadlock-5-10@kernel.org> (raw)
In-Reply-To: <20260916193454.9996-1-kmehltretter@gmail.com>

> [ Upstream commit f1a8f402f13f94263cf349216c257b2985100927 ]
>
> This fixes the following deadlock introduced by 39a92a55be13
> ("bluetooth/l2cap: sync sock recv cb and release")

Queued for 5.10, thanks.

89e856e124f9 ("bluetooth/l2cap: sync sock recv cb and release") is back
on 5.10 as well, so the tree now has both halves rather than the revert.

-- 
Thanks,
Sasha

      reply	other threads:[~2026-09-18  0:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2026091453-unwary-delete-b272@gregkh>
     [not found] ` <daily-reply-20260915-0012-re-l2cap-recv-cb-5-10-revert@kernel.org>
     [not found]   ` <aqoaFdvSsDiiLb5I@gmail.com>
2026-09-16 19:34     ` [PATCH 5.10.y] Bluetooth: L2CAP: Fix deadlock Karl Mehltretter
2026-09-18  0:52       ` Sasha Levin [this message]

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=2026-09-17-daily-reply-0008-l2cap-deadlock-5-10@kernel.org \
    --to=sashal@kernel.org \
    --cc=davem@davemloft.net \
    --cc=eadavis@qq.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=johan.hedberg@gmail.com \
    --cc=kmehltretter@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=luiz.von.dentz@intel.com \
    --cc=marcel@holtmann.org \
    --cc=netdev@vger.kernel.org \
    --cc=patches@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=syzbot+b7f6f8c9303466e16c8a@syzkaller.appspotmail.com \
    /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