| 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
| ||
|
Message-ID: <20160831101028.7ea13fb4@xeon-e3>
Date: Wed, 31 Aug 2016 10:10:28 -0700
From: Stephen Hemminger <stephen@...workplumber.org>
To: David Lebrun <david.lebrun@...ouvain.be>
Cc: <netdev@...r.kernel.org>
Subject: Re: [RFC 2/9] ipv6: sr: add code base for control plane support of
SR-IPv6
On Fri, 26 Aug 2016 17:52:40 +0200
David Lebrun <david.lebrun@...ouvain.be> wrote:
> +
> +static inline struct seg6_pernet_data *seg6_pernet(struct net *net)
> +{
> + return net->ipv6.seg6_data;
> +}
> +
> +static inline void seg6_pernet_lock(struct net *net)
> +{
> + spin_lock(&seg6_pernet(net)->lock);
> +}
> +
> +static inline void seg6_pernet_unlock(struct net *net)
> +{
> + spin_unlock(&seg6_pernet(net)->lock);
> +}
Since these are for control operations why a mutex?
Powered by blists - more mailing lists