linux-kernel - Re: [PATCH] Allow renaming of network interfaces that are up.

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: <20091021103846.2f985ea1@s6510>
Date:	Wed, 21 Oct 2009 10:38:46 +0900
From:	Stephen Hemminger <shemminger@...tta.com>
To:	Nix <nix@...eri.org.uk>
Cc:	Matt Mackall <mpm@...enic.com>, linux-kernel@...r.kernel.org,
	linux-net@...r.kernel.org
Subject: Re: [PATCH] Allow renaming of network interfaces that are up.

On Tue, 20 Oct 2009 19:54:02 +0100
Nix <nix@...eri.org.uk> wrote:

> The ancient restriction banning renaming of busy network interfaces appears
> to be purposeless. Everything that depends on a network interface's name is
> done under the dev_base_lock in any case.
> 
> This makes it much easier to use things like netconsole which bring up a
> network interface before userspace has started: presently these will cause
> interface renamings to fail, breaking any userspace that relies on renaming
> devices to avoid reliance on the potentially-unstable kernel-assigned name.
> 
> Signed-off-by: Nick Alcock <nix@...eri.org.uk>
> ---
>  net/core/dev.c |    2 --
>  1 files changed, 0 insertions(+), 2 deletions(-)

This breaks quagga and other applications that track renames.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/