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]
Date:	Wed, 29 May 2013 13:21:20 -0700
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Oliver Hartkopp <socketcan@...tkopp.net>
Cc:	Linux Netdev List <netdev@...r.kernel.org>
Subject: Re: Does rtnl_lock inhibit incoming traffic?

On Wed, 2013-05-29 at 21:08 +0200, Oliver Hartkopp wrote:
> Hello,
> 
> AFAIK the rtnl_lock is used (at least) to protect the configuration of
> netdevices and routing tables.
> 
> Is the reception of incoming traffic inhibited while the rtnl_lock is set, or
> would i need to protect the data structures to be modified with an additional
> spinlock_bh() / write_lock_bh()?
> 
> Like this one here:
> 
> http://lxr.linux.no/#linux+v3.9.4/net/ipv6/ip6mr.c#L1573


Reception of incoming traffic is not inhibited by rtnl.

And spinlock_bh()/write_lock_bh() only disable current cpu from
receiving frames, but other cpus can still handle incoming traffic.



--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ