netdev - Re: [PATCH v3 net-next] net: core: decouple ifalias get/set from rtnl lock

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: <20171003.155538.1199302288435061105.davem@davemloft.net>
Date:   Tue, 03 Oct 2017 15:55:38 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     fw@...len.de
Cc:     netdev@...r.kernel.org, edumazet@...gle.com
Subject: Re: [PATCH v3 net-next] net: core: decouple ifalias get/set from
 rtnl lock

From: Florian Westphal <fw@...len.de>
Date: Mon,  2 Oct 2017 23:50:05 +0200

> Device alias can be set by either rtnetlink (rtnl is held) or sysfs.
> 
> rtnetlink hold the rtnl mutex, sysfs acquires it for this purpose.
> Add an extra mutex for it and use rcu to protect concurrent accesses.
> 
> This allows the sysfs path to not take rtnl and would later allow
> to not hold it when dumping ifalias.
> 
> Based on suggestion from Eric Dumazet.
> 
> Signed-off-by: Florian Westphal <fw@...len.de>

Applied, thanks Florian.