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-next>] [day] [month] [year] [list]
Message-ID: <52B537B3.3060504@huawei.com>
Date:	Sat, 21 Dec 2013 14:39:47 +0800
From:	Ding Tianhong <dingtianhong@...wei.com>
To:	Jay Vosburgh <fubar@...ibm.com>,
	Andy Gospodarek <andy@...yhouse.net>,
	"David S. Miller" <davem@...emloft.net>,
	Veaceslav Falico <vfalico@...hat.com>,
	Netdev <netdev@...r.kernel.org>,
	Scott Feldman <sfeldma@...ulusnetworks.com>
Subject: [PATCH net-next v2 0/3] bonding: add lp_interval option support and
 simplify the code

The option lp_interval could only be set by sysfs, so add support for loading module.
and update the Documentation/networking/bonding.txt for this option.

Use micro BOND_NO_USE_ARP to simplify the code for mode check.

v2: according to the networking coding style, the patch 01/03 need to cleanup the
    style problem, thanks scott for his advice. The bond_check_param() have too
    many duplicated code with bond sysfs, so I think when scott finish the bond_option_xxx_set(),
    the bond_check_param() should be modify to use the bond_option_xxx_set() function
    to simplify the code.

Ding Tianhong (3):
  bonding: add option lp_interval for loading module
  bonding: ust micro BOND_NO_USE_ARP to simplify the mode check
  bonding: update Documentation/networking/bonding.txt for option
    lp_interval

 Documentation/networking/bonding.txt | 10 ++++++++++
 drivers/net/bonding/bond_main.c      | 29 +++++++++++++++--------------
 2 files changed, 25 insertions(+), 14 deletions(-)

-- 
1.8.0

--
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