netdev - Are xfrm state_add/delete() calls serialized?

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

Date:   Mon, 12 Sep 2022 15:10:12 +0000
From:   Bharat Bhushan <bbhushan2@...vell.com>
To:     "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Are xfrm state_add/delete() calls serialized?

Hi All,

Have a very basic query related to .xdo_dev_state_add()/delete() ops supported by netdev driver. Can .xdo_dev_state_add()/delete() execute from other core while already in process of handling .xdo_dev_state_add()/delete() on one core? Or these calls are always serialized by stack? 
Wanted to know if we need proper locking while handling these ops in driver.

Thanks
-Bharat