linux-kernel - Re: [PATCH] Bluetooth: L2CAP: handle NULL sock pointer in l2cap_sock

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2vj35et6apg2agzztklousifnzt4h2ne6vyjcvb6gxvvpamymu@liqydbn3jb57>
Date: Thu, 9 Jan 2025 18:17:42 +0300
From: Fedor Pchelkin <pchelkin@...ras.ru>
To: Jakub Kicinski <kuba@...nel.org>, 
	Luiz Augusto von Dentz <luiz.dentz@...il.com>
Cc: Johan Hedberg <johan.hedberg@...il.com>, 
	Marcel Holtmann <marcel@...tmann.org>, Ignat Korchagin <ignat@...udflare.com>, 
	Kuniyuki Iwashima <kuniyu@...zon.com>, Eric Dumazet <edumazet@...gle.com>, 
	linux-bluetooth@...r.kernel.org, linux-kernel@...r.kernel.org, lvc-project@...uxtesting.org, 
	netdev@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH] Bluetooth: L2CAP: handle NULL sock pointer in
 l2cap_sock_alloc

On Thu, 09. Jan 07:11, Jakub Kicinski wrote:
> On Thu, 9 Jan 2025 10:47:12 +0300 Fedor Pchelkin wrote:
> > Urgh.. a bit confused about which tree the patch should go to - net or
> > bluetooth.
> > 
> > I've now noticed the Fixes commit went directly via net-next as part of a
> > series (despite "Bluetooth: L2CAP:" patches usually go through bluetooth
> > tree first). So what about this patch?
> 
> 7c4f78cdb8e7 went directly to net-next because it was a larger series touching
> multiple sub-subsystems:

Okay. So I'd expect Luiz to pick up the current patch then, thanks!