netdev - Re: [PATCH net V5 3/3] bonding: change ipsec

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: <20240821171106.69e8e887@kernel.org>
Date: Wed, 21 Aug 2024 17:11:06 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Jay Vosburgh <jv@...sburgh.net>
Cc: Jianbo Liu <jianbol@...dia.com>, netdev@...r.kernel.org,
 davem@...emloft.net, pabeni@...hat.com, edumazet@...gle.com,
 andy@...yhouse.net, saeedm@...dia.com, gal@...dia.com, leonro@...dia.com,
 liuhangbin@...il.com, tariqt@...dia.com
Subject: Re: [PATCH net V5 3/3] bonding: change ipsec_lock from spin lock to
 mutex

On Wed, 21 Aug 2024 09:00:30 -0700 Jay Vosburgh wrote:
> 	Is it really safe to access real_dev once we've left the rcu
> critical section?  What prevents the device referenced by real_dev from
> being deleted as soon as rcu_read_unlock() completes?

Hah, I asked them this question at least 2 times.
Let's see if your superior communication skills help :)