From: patchwork-bot+bluetooth@kernel.org
To: Fedor Pchelkin <pchelkin@ispras.ru>
Cc: luiz.dentz@gmail.com, kuba@kernel.org, johan.hedberg@gmail.com,
marcel@holtmann.org, ignat@cloudflare.com, kuniyu@amazon.com,
edumazet@google.com, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, lvc-project@linuxtesting.org,
netdev@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: L2CAP: handle NULL sock pointer in l2cap_sock_alloc
Date: Thu, 09 Jan 2025 16:16:59 +0000 [thread overview]
Message-ID: <173643941974.1375203.8976214892409778601.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241217211959.279881-1-pchelkin@ispras.ru>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 18 Dec 2024 00:19:59 +0300 you wrote:
> A NULL sock pointer is passed into l2cap_sock_alloc() when it is called
> from l2cap_sock_new_connection_cb() and the error handling paths should
> also be aware of it.
>
> Seemingly a more elegant solution would be to swap bt_sock_alloc() and
> l2cap_chan_create() calls since they are not interdependent to that moment
> but then l2cap_chan_create() adds the soon to be deallocated and still
> dummy-initialized channel to the global list accessible by many L2CAP
> paths. The channel would be removed from the list in short period of time
> but be a bit more straight-forward here and just check for NULL instead of
> changing the order of function calls.
>
> [...]
Here is the summary with links:
- Bluetooth: L2CAP: handle NULL sock pointer in l2cap_sock_alloc
https://git.kernel.org/bluetooth/bluetooth-next/c/a5d2ee08adc1
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:[~2025-01-09 16:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 21:19 [PATCH] Bluetooth: L2CAP: handle NULL sock pointer in l2cap_sock_alloc Fedor Pchelkin
2024-12-21 8:17 ` Kuniyuki Iwashima
2025-01-09 7:47 ` Fedor Pchelkin
2025-01-09 15:11 ` Jakub Kicinski
2025-01-09 15:17 ` Fedor Pchelkin
2025-01-09 16:16 ` 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=173643941974.1375203.8976214892409778601.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=edumazet@google.com \
--cc=ignat@cloudflare.com \
--cc=johan.hedberg@gmail.com \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=lvc-project@linuxtesting.org \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=pchelkin@ispras.ru \
--cc=stable@vger.kernel.org \
/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).