From: patchwork-bot+bluetooth@kernel.org
To: Dmitry Antipov <dmantipov@yandex.ru>
Cc: luiz.dentz@gmail.com, linux-bluetooth@vger.kernel.org,
lvc-project@linuxtesting.org,
syzbot+45ac74737e866894acb0@syzkaller.appspotmail.com
Subject: Re: [PATCH] Bluetooth: l2cap: always unlock channel in l2cap_conless_channel()
Date: Thu, 01 Aug 2024 08:20:35 +0000 [thread overview]
Message-ID: <172250043523.11616.6767698730262967577.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240731091936.476484-1-dmantipov@yandex.ru>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 31 Jul 2024 12:19:36 +0300 you wrote:
> Add missing call to 'l2cap_chan_unlock()' on receive error handling
> path in 'l2cap_conless_channel()'.
>
> Fixes: a24cce144b98 ("Bluetooth: Fix reference counting of global L2CAP channels")
> Reported-by: syzbot+45ac74737e866894acb0@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=45ac74737e866894acb0
> Signed-off-by: Dmitry Antipov <dmantipov@yandex.ru>
>
> [...]
Here is the summary with links:
- Bluetooth: l2cap: always unlock channel in l2cap_conless_channel()
https://git.kernel.org/bluetooth/bluetooth-next/c/1e69bd3ba19c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-08-01 8:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 9:19 [PATCH] Bluetooth: l2cap: always unlock channel in l2cap_conless_channel() Dmitry Antipov
2024-07-31 9:58 ` bluez.test.bot
2024-08-01 8:20 ` patchwork-bot+bluetooth [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=172250043523.11616.6767698730262967577.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=dmantipov@yandex.ru \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=lvc-project@linuxtesting.org \
--cc=syzbot+45ac74737e866894acb0@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.