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: <20140913.163017.945514192048510396.davem@davemloft.net> Date: Sat, 13 Sep 2014 16:30:17 -0400 (EDT) From: David Miller <davem@...emloft.net> To: nikolay@...hat.com Cc: netdev@...r.kernel.org, vfalico@...il.com, j.vosburgh@...il.com, andy@...yhouse.net Subject: Re: [PATCH net-next v2 0/7] bonding: get rid of curr_slave_lock From: Nikolay Aleksandrov <nikolay@...hat.com> Date: Thu, 11 Sep 2014 22:49:21 +0200 > This is the second patch-set dealing with bond locking and the purpose here > is to convert curr_slave_lock into a spinlock called "mode_lock" which can > be used in the various modes for their specific needs. The first three > patches cleanup the use of curr_slave_lock and prepare it for the > conversion which is done in patch 4 and then the modes that were using > their own locks are converted to use the new "mode_lock" giving us the > opportunity to remove their locks. > This patch-set has been tested in each mode by running enslave/release of > slaves in parallel with traffic transmission and miimon=1 i.e. running > all the time. In fact this lead to the discovery of a subtle bug related to > RCU which will be fixed in -net. > Also did an allmodconfig test just in case :-) :-) > v2: fix bond_3ad_state_machine_handler's use of mode_lock and > curr_slave_lock Series applied, thanks. -- 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