From: Jay Vosburgh <jay.vosburgh@canonical.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Mahesh Bandewar
(=?UTF-8?B?4KSu4KS54KWH4KS2IOCkrOCkguCkoeClh+CktQ==?=
=?UTF-8?B?4KS+4KSw?=) <maheshb@google.com>,
Netdev <netdev@vger.kernel.org>,
"Andy Gospodarek" <andy@greyhouse.net>,
"Veaceslav Falico" <vfalico@gmail.com>,
"David Miller" <davem@davemloft.net>,
"Mahesh Bandewar" <mahesh@bandewar.net>
Subject: Re: [PATCH v3 net-next] bonding: pair enable_port with slave_arr_updates
Date: Mon, 07 Feb 2022 09:37:45 -0800 [thread overview]
Message-ID: <8826.1644255465@famine> (raw)
In-Reply-To: <20220207090343.3af1ff59@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Jakub Kicinski <kuba@kernel.org> wrote:
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
>On Sun, 6 Feb 2022 21:52:11 -0800 Mahesh Bandewar (=E0=A4=AE=E0=A4=B9=E0=
=A5=87=E0=A4=B6 =E0=A4=AC=E0=A4=82=E0=A4=A1=E0=A5=87=E0=A4=B5=E0=A4=BE=E0=
=A4=B0) wrote:
>> On Fri, Feb 4, 2022 at 7:59 PM Jakub Kicinski <kuba@kernel.org> wrote:
>> > Quacks like a fix, no? It's tagged for net-next and no fixes tag,
>> > is there a reason why?=20=20
>>=20
>> Though this fixes some corner cases, I couldn't find anything obvious
>> that I can report as "fixes" hence decided otherwise. Does that make
>> sense?
>
>So it's was not introduced in the refactorings which added
>update_slave_arr? If the problem existed forever we can put:
>
>Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
>
>it's just an indication how far back the backporting should go.
>For anything older than oldest LTS (4.9) the exact tag probably
>doesn't matter all that much.
I think the correct Fixes line would be the commit that
introduces the array logic in the first place, which I believe is:
Fixes: ee6377147409 ("bonding: Simplify the xmit function for modes that us=
e xmit_hash")
This dates to 3.18.
-J
---
-Jay Vosburgh, jay.vosburgh@canonical.com
next prev parent reply other threads:[~2022-02-07 17:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 0:06 [PATCH v3 net-next] bonding: pair enable_port with slave_arr_updates Mahesh Bandewar
2022-02-04 0:50 ` Jay Vosburgh
2022-02-05 3:59 ` Jakub Kicinski
2022-02-07 5:52 ` Mahesh Bandewar (महेश बंडेवार)
2022-02-07 17:03 ` Jakub Kicinski
2022-02-07 17:37 ` Jay Vosburgh [this message]
2022-02-07 22:18 ` Mahesh Bandewar (महेश बंडेवार)
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=8826.1644255465@famine \
--to=jay.vosburgh@canonical.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=mahesh@bandewar.net \
--cc=maheshb@google.com \
--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;
as well as URLs for NNTP newsgroup(s).