netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vincent Bernat <vincent@bernat.ch>
To: Michal Soltys <soltys@ziu.info>
Cc: Mahesh Bandewar <mahesh@bandewar.net>,
	Jay Vosburgh <j.vosburgh@gmail.com>,
	Andy Gospodarek <andy@greyhouse.net>,
	Veaceslav Falico <vfalico@gmail.com>,
	David Miller <davem@davemloft.net>,
	Netdev <netdev@vger.kernel.org>,
	Mahesh Bandewar <maheshb@google.com>,
	Chonggang Li <chonggangli@google.com>
Subject: Re: [next] bonding: pass link-local packets to bonding master also.
Date: Thu, 20 Dec 2018 06:55:45 +0100	[thread overview]
Message-ID: <87ftuseo7y.fsf@bernat.ch> (raw)
In-Reply-To: <120845b4-3828-4473-19bc-ec3ab0b49d4c@ziu.info> (Michal Soltys's message of "Wed, 19 Dec 2018 23:57:13 +0100")

 ❦ 19 décembre 2018 23:57 +01, Michal Soltys <soltys@ziu.info>:

>>> 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.
>> 
>> Unfortunately, this doesn't completely restore the previous
>> functionality as PACKET_ORIGDEV is broken for the copy: the original
>> interface is lost through the call to netif_rx(). A LLDP daemon
>> listening to the master interface won't get the original interface like
>> it was able to before 4.12.
>> 
>> I am a bit lost of what the original patch was trying to achieve. I am
>> using the following test program:
>> 
>
> Basing on what you wrote below, it seems that everything was already
> possible before the Chonggang Li's commit ?
>
> If I understand correctly:
>
> - if listening on master, you could get both slave interface
> (PACKET_ORIGDEV) as well as bonding master
> - if listening on slave, you would just get the slave interface
>
> Right ?

Yes. This has been this way since 2.6.27.
-- 
Test programs at their boundary values.
            - The Elements of Programming Style (Kernighan & Plauger)

  reply	other threads:[~2018-12-20  5:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-16  1:12 [PATCH next] bonding: pass link-local packets to bonding master also Mahesh Bandewar
2018-07-16 21:24 ` Jay Vosburgh
2018-07-16 23:53   ` Mahesh Bandewar (महेश बंडेवार)
2018-07-17  9:32     ` Michal Soltys
2018-07-17 22:17       ` Michal Soltys
2018-07-16 23:33 ` Stephen Hemminger
2018-07-16 23:57   ` Mahesh Bandewar (महेश बंडेवार)
2018-07-17  0:43     ` Stephen Hemminger
2018-07-17  9:55     ` Michal Soltys
2018-11-30 21:32 ` [next] " Vincent Bernat
2018-12-09  8:30   ` Vincent Bernat
2018-12-19 22:57   ` Michal Soltys
2018-12-20  5:55     ` Vincent Bernat [this message]
2018-12-23 13:06       ` Michal Soltys
2018-12-23 13:16         ` Vincent Bernat

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=87ftuseo7y.fsf@bernat.ch \
    --to=vincent@bernat.ch \
    --cc=andy@greyhouse.net \
    --cc=chonggangli@google.com \
    --cc=davem@davemloft.net \
    --cc=j.vosburgh@gmail.com \
    --cc=mahesh@bandewar.net \
    --cc=maheshb@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=soltys@ziu.info \
    --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).