From: Nikolay Aleksandrov <nikolay@redhat.com>
To: netdev@vger.kernel.org
Cc: fubar@us.ibm.com, davem@davemloft.net, andy@greyhouse.net,
mleitner@redhat.com
Subject: Re: [PATCH -net 0/2] bonding: fix arp_validate desync state & race
Date: Fri, 06 Sep 2013 22:10:58 +0200 [thread overview]
Message-ID: <522A36D2.1080306@redhat.com> (raw)
In-Reply-To: <1378496518-16104-1-git-send-email-nikolay@redhat.com>
On 09/06/2013 09:41 PM, Nikolay Aleksandrov wrote:
> Hello all,
> These two patches aim to fix the possible de-sync state which the bond
> can enter if we have arp_validate without arp_interval or the other way
> around. They also fix a race condition between arp_validate setting and
> mode changing.
>
> Patch 01 - fixes the race condition between store_arp_validate and bond
> mode change by using rtnl for sync
> Patch 02 - fixes the possible de-sync state by setting/unsetting recv_probe
> if arp_interval is set/unset and also if arp_validate is set/unset
>
> Best regards,
> Nikolay Aleksandrov
>
>
> Nikolay Aleksandrov (2):
> bonding: fix store_arp_validate race with mode change
> bonding: fix bond_arp_rcv setting and arp validate desync state
>
> drivers/net/bonding/bond_main.c | 4 ++--
> drivers/net/bonding/bond_sysfs.c | 31 +++++++++++++++++++++++++------
> drivers/net/bonding/bonding.h | 1 +
> 3 files changed, 28 insertions(+), 8 deletions(-)
>
Ugh, self-nack I just noticed the mode check in store_arp_validate passes
if new_value is 0.
I'll wait some time to see if there isn't anything else and re-post.
Cheers,
Nik
prev parent reply other threads:[~2013-09-06 20:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-06 19:41 [PATCH -net 0/2] bonding: fix arp_validate desync state & race Nikolay Aleksandrov
2013-09-06 19:41 ` [PATCH -net 1/2] bonding: fix store_arp_validate race with mode change Nikolay Aleksandrov
2013-09-06 19:41 ` [PATCH -net 2/2] bonding: fix bond_arp_rcv setting and arp validate desync state Nikolay Aleksandrov
2013-09-06 20:10 ` Nikolay Aleksandrov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=522A36D2.1080306@redhat.com \
--to=nikolay@redhat.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=fubar@us.ibm.com \
--cc=mleitner@redhat.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).