netdev - Re: [PATCH 0/2] bring UP loopback device at initialziation

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: <20170705.092032.1482668095877350196.davem@davemloft.net>
Date:   Wed, 05 Jul 2017 09:20:32 +0100 (WEST)
From:   David Miller <davem@...emloft.net>
To:     mahesh@...dewar.net
Cc:     jmorris@...ei.org, yoshfuji@...ux-ipv6.org, kaber@...sh.net,
        edumazet@...gle.com, ebiederm@...ssion.com, netdev@...r.kernel.org,
        maheshb@...gle.com
Subject: Re: [PATCH 0/2] bring UP loopback device at initialziation

From: Mahesh Bandewar <mahesh@...dewar.net>
Date: Tue,  4 Jul 2017 12:16:15 -0700

> In almost every scenario the loopback device is brought UP after
> initialization. So there is no point of bringing up the device in
> DOWN state followed by device UP operation. This change exposed
> another issue of fib-trie initialization which is corrected in the 
> first path.

You use the word almost, which supports my position that someone may
not want this.

I also don't see it as so much of a burdon to bring the lo device up
explicitly.  Systems have been having to do that since the beginning
of time.

Sorry I'm not applying this.