netdev - Re: restoring IP multicast addresses when restarting the interface.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120424153023.0913956e@asterix.rh>
Date:	Tue, 24 Apr 2012 15:30:23 -0300
From:	Flavio Leitner <fbl@...hat.com>
To:	Herbert Xu <herbert@...dor.hengli.com.au>
Cc:	netdev <netdev@...r.kernel.org>, David Miller <davem@...emloft.net>
Subject: Re: restoring IP multicast addresses when restarting the interface.

On Mon, 23 Apr 2012 22:14:25 +1000
Herbert Xu <herbert@...dor.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?

thanks,
fbl
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html