netdev - Re: [patch net-next] ipv4: loopback device: ignore value changes after device is upped

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]

Date:	Tue, 07 Jan 2014 15:55:49 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	jiri@...nulli.us
Cc:	netdev@...r.kernel.org, kuznet@....inr.ac.ru, jmorris@...ei.org,
	yoshfuji@...ux-ipv6.org, kaber@...sh.net,
	hannes@...essinduktion.org
Subject: Re: [patch net-next] ipv4: loopback device: ignore value changes
 after device is upped

From: Jiri Pirko <jiri@...nulli.us>
Date: Tue,  7 Jan 2014 15:55:45 +0100

> When lo is brought up, new ifa is created. Then, devconf and neigh values
> bitfield should be set so later changes of default values would not
> affect lo values.
> 
> Note that the same behaviour is in ipv6. Also note that this is likely
> not an issue in many distros (for example Fedora 19) because userspace
> sets address to lo manually before bringing it up.
> 
> Signed-off-by: Jiri Pirko <jiri@...nulli.us>

Looks good, applied.
--
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