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] [day] [month] [year] [list]
Message-Id: <20081013.113726.193048941.davem@davemloft.net>
Date:	Mon, 13 Oct 2008 11:37:26 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	adwol@...k.pl
Cc:	akpm@...ux-foundation.org, netdev@...r.kernel.org,
	bugme-daemon@...zilla.kernel.org
Subject: Re: [Bugme-new] [Bug 11655] New: /proc/sys/net/ipv6/conf/all/*
 controls don't work

From: Adam Osuchowski <adwol@...k.pl>
Date: Mon, 13 Oct 2008 12:13:34 +0200

> David Miller wrote:
> > Not a bug.
> > 
> > These "global" setting have to be set to the desired value before the
> > device is created.  And it is at creation time that these global
> > values are "inherited" by the device.
> > 
> > Afterwards changes to the global value will not propagate to those
> > devices again, because that might override a changed setting made
> > by the user.
> > 
> > It is only newly created devices which get these values.
> 
> I understand you are talking about /proc/sys/net/ipv6/conf/default/*
> controls. If so, it's ok, but I talked about /proc/sys/net/ipv6/conf/all/*
> controls. Documentation/networking/ip-sysctl.txt says:
> 
>     conf/default/*:
> 	    Change the interface-specific default settings.
> 
> 
>     conf/all/*:
> 	    Change all the interface-specific settings.
> 
> so what is the difference between default and all in the context of your
> statement? In my opinion, it could be understood that default settings
> are inherited and those from "all" directory change values for all
> current devices.

Unfortunately not all "all" knobs are treated universally, only some
of them all.

If you grep for "devconf_all" under net/ipv6 you'll see which ones
get used and in what manner.

Of course, we'll need to tweak either the docs or the implementation
to match :-)
--
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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ