linux-kernel - Re: [PATCH net 3/8] idpf: fix possible race in idpf_vport

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] [day] [month] [year] [list]

Message-ID: <20251013111352.5ff15ec3@kernel.org>
Date: Mon, 13 Oct 2025 11:13:52 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Jacob Keller <jacob.e.keller@...el.com>
Cc: "Tantilov, Emil S" <emil.s.tantilov@...el.com>, Przemek Kitszel
 <przemyslaw.kitszel@...el.com>, Andrew Lunn <andrew+netdev@...n.ch>, "David
 S. Miller" <davem@...emloft.net>, "Eric Dumazet" <edumazet@...gle.com>,
 Paolo Abeni <pabeni@...hat.com>, "Pavan Kumar Linga"
 <pavan.kumar.linga@...el.com>, Alexander Lobakin
 <aleksander.lobakin@...el.com>, Willem de Bruijn <willemb@...gle.com>,
 Sridhar Samudrala <sridhar.samudrala@...el.com>, Phani Burra
 <phani.r.burra@...el.com>, Piotr Kwapulinski <piotr.kwapulinski@...el.com>,
 Simon Horman <horms@...nel.org>, Radoslaw Tyl <radoslawx.tyl@...el.com>,
 Jedrzej Jagielski <jedrzej.jagielski@...el.com>, Mateusz Polchlopek
 <mateusz.polchlopek@...el.com>, Anton Nadezhdin
 <anton.nadezhdin@...el.com>, Konstantin Ilichev
 <konstantin.ilichev@...el.com>, Milena Olech <milena.olech@...el.com>,
 <netdev@...r.kernel.org>, <linux-kernel@...r.kernel.org>, Joshua Hay
 <joshua.a.hay@...el.com>, Aleksandr Loktionov
 <aleksandr.loktionov@...el.com>, Chittim Madhu <madhu.chittim@...el.com>,
 Samuel Salin <Samuel.salin@...el.com>
Subject: Re: [PATCH net 3/8] idpf: fix possible race in idpf_vport_stop()

On Wed, 8 Oct 2025 14:41:40 -0700 Jacob Keller wrote:
> Jakub, from this thread it still seems like you won't accept this patch
> as-is?

I haven't analyzed Emil's response. I hope my concern is clear enough
(at least to you). If the code is provably safe I think the patch itself
can go in, we just need a much better commit msg.