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>] [day] [month] [year] [list]
Message-ID: <d2d3f366-4082-cc0f-7b3a-73573ef887b6@ucloud.cn>
Date:   Mon, 10 Jun 2019 16:22:42 +0800
From:   wenxu <wenxu@...oud.cn>
To:     Linux Kernel Network Developers <netdev@...r.kernel.org>
Subject: rtnetlink dump operations also share the rrtnl_mutex

Hi all,


When a netlink_route socket was created, the nlk->cb_mutex is get through nl_table[NETLINK_ROUTE].cb_mutex which is the rtnl_mutex.


So all the netlink_route dump operation can contend for each other (ip l, ip a, ip r, tc ls). It will also contend with other RTM_NEW/DEL operations.


So there can be a good way for each msgtype have their own mutex for dump operations?


BR

wenxu



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ