From: Paolo Abeni <pabeni@redhat.com>
To: Jonathan Toppins <jtoppins@redhat.com>,
netdev@vger.kernel.org, Jay Vosburgh <j.vosburgh@gmail.com>
Cc: Veaceslav Falico <vfalico@gmail.com>,
Andy Gospodarek <andy@greyhouse.net>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 2/2] bonding: fix link recovery in mode 2 when updelay is nonzero
Date: Tue, 22 Nov 2022 11:59:51 +0100 [thread overview]
Message-ID: <38fbc36783d583f805f30fb3a55a8a87f67b59ac.camel@redhat.com> (raw)
In-Reply-To: <cb89b92af89973ee049a696c362b4a2abfdd9b82.1668800711.git.jtoppins@redhat.com>
Hello,
On Fri, 2022-11-18 at 15:30 -0500, Jonathan Toppins wrote:
> Before this change when a bond in mode 2 lost link, all of its slaves
> lost link, the bonding device would never recover even after the
> expiration of updelay. This change removes the updelay when the bond
> currently has no usable links. Conforming to bonding.txt section 13.1
> paragraph 4.
>
> Signed-off-by: Jonathan Toppins <jtoppins@redhat.com>
Why are you targeting net-next? This looks like something suitable to
the -net tree to me. If, so could you please include a Fixes tag?
Note that we can add new self-tests even via the -net tree.
Thanks,
Paolo
next prev parent reply other threads:[~2022-11-22 11:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1668800711.git.jtoppins@redhat.com>
2022-11-18 20:30 ` [PATCH net-next 1/2] selftests: bonding: up/down delay w/ slave link flapping Jonathan Toppins
2022-11-22 10:53 ` Paolo Abeni
2022-11-18 20:30 ` [PATCH net-next 2/2] bonding: fix link recovery in mode 2 when updelay is nonzero Jonathan Toppins
2022-11-22 10:59 ` Paolo Abeni [this message]
2022-11-22 13:36 ` Jonathan Toppins
2022-11-22 14:45 ` Paolo Abeni
2022-11-22 15:37 ` Jonathan Toppins
2022-11-22 21:12 ` Nikolay Aleksandrov
2022-11-22 21:15 ` Nikolay Aleksandrov
2022-11-22 21:17 ` Jonathan Toppins
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=38fbc36783d583f805f30fb3a55a8a87f67b59ac.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=j.vosburgh@gmail.com \
--cc=jtoppins@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vfalico@gmail.com \
/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