netdev - Re: ipv6: why disable ipv6 on last address removal?

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: <20100104.224436.107234750.davem@davemloft.net>
Date:	Mon, 04 Jan 2010 22:44:36 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	yoshfuji@...ux-ipv6.org
Cc:	jbohac@...e.cz, netdev@...r.kernel.org
Subject: Re: ipv6: why disable ipv6 on last address removal?

From: YOSHIFUJI Hideaki <yoshfuji@...ux-ipv6.org>
Date: Wed, 09 Dec 2009 16:39:15 +0900

> Well, AFAIK, it is basically ancient thing.
> Some (rather new) paramters are exactly related bringing
> up each interface.
> 
> Such parameters should be set _before_ it is brought up.
> For now, people can do this using the "default" value.

I think we should retain inet6 device private structure after
we allocate it the first time that an ipv6 action occurs for
the device, exactly so that settings made earlier can be
retained.

--
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