All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: nikolay@cumulusnetworks.com
Cc: netdev@vger.kernel.org, roopa@cumulusnetworks.com,
	bridge@lists.linux-foundation.org
Subject: Re: [PATCH net] net: bridge: mcast: don't delete permanent entries when fast leave is enabled
Date: Wed, 31 Jul 2019 19:04:13 -0400 (EDT)	[thread overview]
Message-ID: <20190731.190413.1782006239456872904.davem@davemloft.net> (raw)
In-Reply-To: <20190730112100.18156-1-nikolay@cumulusnetworks.com>

From: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
Date: Tue, 30 Jul 2019 14:21:00 +0300

> When permanent entries were introduced by the commit below, they were
> exempt from timing out and thus igmp leave wouldn't affect them unless
> fast leave was enabled on the port which was added before permanent
> entries existed. It shouldn't matter if fast leave is enabled or not
> if the user added a permanent entry it shouldn't be deleted on igmp
> leave.
 ...
> Fixes: ccb1c31a7a87 ("bridge: add flags to distinguish permanent mdb entires")
> Signed-off-by: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>

Applied and queued up for -stable.

WARNING: multiple messages have this Message-ID (diff)
From: David Miller <davem@davemloft.net>
To: nikolay@cumulusnetworks.com
Cc: netdev@vger.kernel.org, roopa@cumulusnetworks.com,
	bridge@lists.linux-foundation.org
Subject: Re: [Bridge] [PATCH net] net: bridge: mcast: don't delete permanent entries when fast leave is enabled
Date: Wed, 31 Jul 2019 19:04:13 -0400 (EDT)	[thread overview]
Message-ID: <20190731.190413.1782006239456872904.davem@davemloft.net> (raw)
In-Reply-To: <20190730112100.18156-1-nikolay@cumulusnetworks.com>

From: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
Date: Tue, 30 Jul 2019 14:21:00 +0300

> When permanent entries were introduced by the commit below, they were
> exempt from timing out and thus igmp leave wouldn't affect them unless
> fast leave was enabled on the port which was added before permanent
> entries existed. It shouldn't matter if fast leave is enabled or not
> if the user added a permanent entry it shouldn't be deleted on igmp
> leave.
 ...
> Fixes: ccb1c31a7a87 ("bridge: add flags to distinguish permanent mdb entires")
> Signed-off-by: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>

Applied and queued up for -stable.

  parent reply	other threads:[~2019-07-31 23:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-30 11:21 [PATCH net] net: bridge: mcast: don't delete permanent entries when fast leave is enabled Nikolay Aleksandrov
2019-07-30 11:21 ` [Bridge] " Nikolay Aleksandrov
2019-07-30 13:58 ` David Ahern
2019-07-30 13:58   ` [Bridge] " David Ahern
2019-07-30 14:00   ` Nikolay Aleksandrov
2019-07-30 14:00     ` [Bridge] " Nikolay Aleksandrov
2019-07-30 17:18 ` David Miller
2019-07-30 17:18   ` [Bridge] " David Miller
2019-07-30 17:21   ` Nikolay Aleksandrov
2019-07-30 17:21     ` [Bridge] " Nikolay Aleksandrov
2019-07-30 17:23     ` Nikolay Aleksandrov
2019-07-30 17:23       ` [Bridge] " Nikolay Aleksandrov
2019-07-31 23:04 ` David Miller [this message]
2019-07-31 23:04   ` David Miller

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=20190731.190413.1782006239456872904.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=bridge@lists.linux-foundation.org \
    --cc=netdev@vger.kernel.org \
    --cc=nikolay@cumulusnetworks.com \
    --cc=roopa@cumulusnetworks.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.