netdev - bridge carrier issue

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20110920.152953.448244771460257273.davem@redhat.com>
Date:	Tue, 20 Sep 2011 15:29:53 -0400 (EDT)
From:	David Miller <davem@...hat.com>
To:	netdev@...r.kernel.org
CC:	shemminger@...tta.com
Subject: bridge carrier issue

I'm marking the patches in patchwork on this as "deferred".

It is my opinion that we need to push back on the virtualization stuff
because otherwise it is impossible for network manager and friends to
operate properly.

Without the carrier going on only when a device is actually attached
and operating, NM has no "signal" to know when it actually should do
DHCP and whatnot.

On the other hand, the virtualization tools and libraries can operate
properly within the constraints added by the carrier behavior we have
now.

And I also believe they can do so in a way that allows them to work
on kernels before the carrier change.

Therefore, the only way to move forward and get everything working is
to change the virtualization tools.
--
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