linux-kernel - why does kernel 3.8-rc1 put all TAP devices into state RUNNING during boot

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-next>] [day] [month] [year] [list]

Date:	Sat, 05 Jan 2013 11:16:25 +0100
From:	Toralf Förster <toralf.foerster@....de>
To:	Maxim Krasnyansky <maxk@....qualcomm.com>
CC:	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: why does kernel 3.8-rc1 put all TAP devices into state RUNNING during
 boot

At my stable Gentoo Linux I'm observed a change behaviour for the
configured TAP devices after the boot process.

$ diff 3.7.1 3.8.0-rc1+ | grep UP
< br0: flags=4355<UP,BROADCAST,PROMISC,MULTICAST>  mtu 1500
> br0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST>  mtu 1500
< tap0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
> tap0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500


May I ask you if this changed behaviour is intended ?


FWIW I configured those devices at that system in this way :

$ head -n 20 /etc/conf.d/net
# /etc/conf.d/net
#

#       KVM
#
bridge_br0="tap0 tap1 tap2 tap3"
config_br0="192.168.0.254/8"
brctl_br0="setfd 0
sethello 10
stp off"
rc_net_br0_need="net.tap0 net.tap1 net.tap2 net.tap3"

config_tap0="null"
tuntap_tap0="tap"
tunctl_tap0="-u <me>"

...

-- 
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
--
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/