From: David Miller <davem@davemloft.net>
To: fbl@redhat.com
Cc: herbert@gondor.hengli.com.au, netdev@vger.kernel.org
Subject: Re: restoring IP multicast addresses when restarting the interface.
Date: Tue, 24 Apr 2012 17:00:04 -0400 (EDT) [thread overview]
Message-ID: <20120424.170004.1811627706738841106.davem@davemloft.net> (raw)
In-Reply-To: <20120424153023.0913956e@asterix.rh>
From: Flavio Leitner <fbl@redhat.com>
Date: Tue, 24 Apr 2012 15:30:23 -0300
> On Mon, 23 Apr 2012 22:14:25 +1000
> Herbert Xu <herbert@gondor.hengli.com.au> wrote:
>
>> On Fri, Apr 20, 2012 at 09:25:33PM -0300, Flavio Leitner wrote:
>> >
>> > Although the new behavior seems nice and save some user space
>> > work, I think it was unintentional and likely to be a bug.
>> >
>> > What you guys think?
>>
>> Are you talking about multicast subscriptions on the interface?
>
> Yes.
>
>> I don't see why they should disappear when the interface goes
>> down and then comes back up since these ultimately come from
>> application sockets which continue to exist after a down/up.
>
> Yeah, but that's not how things used to work before, so my
> question is if the kernel should be responsible for keeping
> the subscription or the application.
>
> If the admin puts down the interface and remove the module,
> for instance, then the multicast subscription is gone.
> Should the application monitor for that then?
>
> David? Any thoughts?
David Stevens at IBM and Herbert at the current multicast
experts, so I will defer to them.
next prev parent reply other threads:[~2012-04-24 21:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-21 0:25 restoring IP multicast addresses when restarting the interface Flavio Leitner
2012-04-23 12:14 ` Herbert Xu
2012-04-24 18:30 ` Flavio Leitner
2012-04-24 21:00 ` David Miller [this message]
2012-04-24 21:28 ` David Stevens
2012-04-24 22:19 ` Flavio Leitner
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=20120424.170004.1811627706738841106.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=fbl@redhat.com \
--cc=herbert@gondor.hengli.com.au \
--cc=netdev@vger.kernel.org \
/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.