From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: daniel <daniel@dd-wrt.com>
Cc: netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
"David S. Miller" <davem@davemloft.net>,
Ulrich Weber <ulrich.weber@sophos.com>
Subject: Re: [PATCH] Bridge: Fix ipv6 mc snooping if it has no ipv6 address.
Date: Thu, 23 Jun 2016 20:42:42 +0200 [thread overview]
Message-ID: <20160623184242.GC5511@otheros> (raw)
In-Reply-To: <4375d883-a95f-d032-c678-ed2fd665c36b@dd-wrt.com>
Hi Daniel,
Thanks for submitting this patch here :).
On Thu, Jun 23, 2016 at 11:28:55AM +0200, daniel wrote:
> The bridge is falsly dropping ipv6 mulitcast packets
> if there is no ipv6 address assigned on the brigde and no
> external mld querier is present.
and if the bridge internal querier is enabled (usually disabled
by default in the bridge code, but enabled by default in OpenWRT
for instance).
>
> When the bridge fails to build mld queries, because it has no
> ipv6 address, it silently returns, but keeps the local querier enabled.
> (br_multicast.c:832)
Not sure whether David or others like line numbers in commit messages, as
they can change over time.
>
> Ipv6 multicast snooping can only work if:
> a) an external querier is present
maybe clarify that this is an OR, not AND?
I think you can add a [PATCH net] tag, as it seems small
enough for stable kernels and fixes a potential, confusing packet
loss case.
Also maybe add a:
--
Fixes: 1d81d4c3dd88 ("bridge: check return value of ipv6_dev_get_saddr()")
--
Regards, Linus
PS: Does not seem to apply for me on either David's net branch or
Torvald's master branch.
"fatal: patch fragment without header at line 7: @@ -599,10
+612,12 @@ static inline bool"
Try using "git format-patch" and "git send-email" instead. Also
check ./scripts/get_maintainer.pl for a few more email addresses
to add.
prev parent reply other threads:[~2016-06-23 18:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-23 9:28 [PATCH] Bridge: Fix ipv6 mc snooping if it has no ipv6 address daniel
2016-06-23 18:42 ` Linus Lüssing [this message]
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=20160623184242.GC5511@otheros \
--to=linus.luessing@c0d3.blue \
--cc=bridge@lists.linux-foundation.org \
--cc=daniel@dd-wrt.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=ulrich.weber@sophos.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).