From: Jakub Kicinski <kuba@kernel.org>
To: Jay Vosburgh <jay.vosburgh@canonical.com>
Cc: Paolo Abeni <pabeni@redhat.com>,
Vladimir Oltean <vladimir.oltean@nxp.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>, Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Jonathan Toppins <jtoppins@redhat.com>,
Veaceslav Falico <vfalico@gmail.com>,
Andy Gospodarek <andy@greyhouse.net>,
Hangbin Liu <liuhangbin@gmail.com>,
Jamal Hadi Salim <jhs@mojatatu.com>,
Cong Wang <xiyou.wangcong@gmail.com>,
Jiri Pirko <jiri@resnulli.us>,
Nikolay Aleksandrov <razor@blackwall.org>,
Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [PATCH v3 net 1/4] net: bonding: replace dev_trans_start() with the jiffies of the last ARP/NS
Date: Tue, 2 Aug 2022 13:33:42 -0700 [thread overview]
Message-ID: <20220802133342.1ac7531a@kernel.org> (raw)
In-Reply-To: <23020.1659471874@famine>
On Tue, 02 Aug 2022 13:24:34 -0700 Jay Vosburgh wrote:
> >One more time, sorry :) If I'm reading things right Vladimir and
> >I would like this to be part of 5.20, Paolo is okay with that,
> >Jay would prefer to delay it until 5.21.
> >
> >Is that right?
>
> I'm sure there's an Abbott & Costello joke in here somewhere,
> but I thought Paolo preferred net-next, and I said I was ok with that.
:D
> >My preference for 5.20 is because we do have active users reporting
> >problems in stable, and by moving to 5.21 we're delaying things by
> >2 weeks. At the same time, 5.20 vs 5.21 doesn't matter as we intend
> >to hit stable users with these change before either of those is out.
>
> I have no objection to 5.20 if you & Paolo don't object.
>
> For stable, I believe that 1/4 (and 4/4 for docs) is the minimum
> set to resolve the functional issues; is the plan to send all 4 patches
> to stable, or just 1 and 4?
1 & 4 for stable SGTM.
> I do think this patch does widen the scope of failures that may
> go undetected on the TX side, but most of the time the failure to
> receive the ARP on the RX side should cover for that. Regardless,
> that's a concern for later that doesn't need to be hashed out right now.
next prev parent reply other threads:[~2022-08-02 20:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-31 12:41 [PATCH v3 net 0/4] Make DSA work with bonding's ARP monitor Vladimir Oltean
2022-07-31 12:41 ` [PATCH v3 net 1/4] net: bonding: replace dev_trans_start() with the jiffies of the last ARP/NS Vladimir Oltean
2022-07-31 18:53 ` Jay Vosburgh
2022-07-31 19:13 ` Vladimir Oltean
2022-08-02 1:04 ` Jay Vosburgh
2022-08-02 1:45 ` Vladimir Oltean
2022-08-02 9:05 ` Paolo Abeni
2022-08-02 16:11 ` Jakub Kicinski
2022-08-02 16:29 ` Jay Vosburgh
2022-08-02 16:30 ` Vladimir Oltean
2022-08-02 17:33 ` Paolo Abeni
2022-08-02 18:00 ` Jay Vosburgh
2022-08-02 19:10 ` Jakub Kicinski
2022-08-02 20:24 ` Jay Vosburgh
2022-08-02 20:33 ` Jakub Kicinski [this message]
2022-08-02 20:34 ` Paolo Abeni
2022-07-31 12:41 ` [PATCH v3 net 2/4] net/sched: remove hacks added to dev_trans_start() for bonding to work Vladimir Oltean
2022-07-31 12:41 ` [PATCH v3 net 3/4] Revert "veth: Add updating of trans_start" Vladimir Oltean
2022-07-31 12:41 ` [PATCH v3 net 4/4] docs: net: bonding: remove mentions of trans_start Vladimir Oltean
2022-08-01 17:58 ` [PATCH v3 net 0/4] Make DSA work with bonding's ARP monitor Jakub Kicinski
2022-08-01 23:39 ` Vladimir Oltean
2022-08-04 2:40 ` patchwork-bot+netdevbpf
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=20220802133342.1ac7531a@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=jay.vosburgh@canonical.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=jtoppins@redhat.com \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--cc=stephen@networkplumber.org \
--cc=vfalico@gmail.com \
--cc=vivien.didelot@gmail.com \
--cc=vladimir.oltean@nxp.com \
--cc=xiyou.wangcong@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.