From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: [PATCH next] bonding: pass link-local packets to bonding master also. Date: Mon, 16 Jul 2018 17:43:49 -0700 Message-ID: <20180716174349.0489c091@xeon-e3> References: <20180716011246.225647-1-mahesh@bandewar.net> <20180716163353.2fe5659c@xeon-e3> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: Mahesh Bandewar , Jay Vosburgh , Andy Gospodarek , Veaceslav Falico , David Miller , Netdev , Michal Soltys To: "Mahesh Bandewar (=?UTF-8?B?4KSu4KS54KWH4KS2IOCkrOCkguCkoeClh+CktQ==?= =?UTF-8?B?4KS+4KSw?=)" Return-path: Received: from mail-pl0-f66.google.com ([209.85.160.66]:40016 "EHLO mail-pl0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729228AbeGQBNp (ORCPT ); Mon, 16 Jul 2018 21:13:45 -0400 Received: by mail-pl0-f66.google.com with SMTP id s17-v6so6614673plp.7 for ; Mon, 16 Jul 2018 17:43:52 -0700 (PDT) In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On Mon, 16 Jul 2018 16:57:22 -0700 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 Mon, Jul 16, 2018 at 4:33 PM, Stephen Hemminger > wrote: > > On Sun, 15 Jul 2018 18:12:46 -0700 > > Mahesh Bandewar wrote: > > =20 > >> From: Mahesh Bandewar > >> > >> Commit b89f04c61efe ("bonding: deliver link-local packets with > >> skb->dev set to link that packets arrived on") changed the behavior > >> of how link-local-multicast packets are processed. The change in > >> the behavior broke some legacy use cases where these packets are > >> expected to arrive on bonding master device also. > >> > >> This patch passes the packet to the stack with the link it arrived > >> on as well as passes to the bonding-master device to preserve the > >> legacy use case. > >> > >> Reported-by: Michal Soltys > >> Signed-off-by: Mahesh Bandewar =20 > > > > Thanks for fixing this. > > > > Why not add a Fixes: tag instead of just talking about the commit? > > That helps the stable maintainers know which versions of the kernel > > need the patch. =20 > Well, I thought about it. It's definitely 'related' but not sure it > 'fixes' in true sense. It definitely fixes the broken legacy case > though. Is that sufficient to add 'fixes' tag? The previous commit caused a regression. your change fixes the regression