| 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
| ||
|
Message-ID: <20061219155133.20132824@freekitty> Date: Tue, 19 Dec 2006 15:51:33 -0800 From: Stephen Hemminger <shemminger@...l.org> To: Rick Jones <rick.jones2@...com> Cc: Arjan van de Ven <arjan@...radead.org>, Matthew Garrett <mjg59@...f.ucam.org>, linux-kernel@...r.kernel.org, netdev@...r.kernel.org Subject: Re: Network drivers that don't suspend on interface down On Wed, 20 Dec 2006 15:37:41 -0800 Rick Jones <rick.jones2@...com> wrote: > > There are two different problems: > > > > 1) Behavior seems to be different depending on device driver > > author. We should document the expected semantics better. > > > > IMHO: > > When device is down, it should: > > a) use as few resources as possible: > > - not grab memory for buffers > > - not assign IRQ unless it could get one > > - turn off all power consumption possible > > b) allow setting parameters like speed/duplex/autonegotiation, > > ring buffers, ... with ethtool, and remember the state > > c) not accept data coming in, and drop packets queued > > What implications does c have for something like tcpdump? > > rick jones None, you can bring up the device without actually assigning an address to it. -- Stephen Hemminger <shemminger@...l.org> - 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/
Powered by blists - more mailing lists