netdev - Re: [patch 1/3] [PATCH] qeth: HiperSockets Network Traffic Analyzer

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]

Date:	Tue, 12 Jan 2010 04:59:44 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	ubraun@...ux.vnet.ibm.com
Cc:	netdev@...r.kernel.org, linux-s390@...r.kernel.org,
	frank.blaschka@...ibm.com, ursula.braun@...ibm.com
Subject: Re: [patch 1/3] [PATCH] qeth: HiperSockets Network Traffic Analyzer

From: Ursula Braun <ubraun@...ux.vnet.ibm.com>
Date: Tue, 12 Jan 2010 13:25:31 +0100

> Sounds like a good idea, but there exists a qeth-specific problem if
> sniffer configuration should be switched to ethtool: Ethtool requires
> the existence of the network interface for the network device. The
> network interface for s390 network devices is defined within an
> s390-specific initialization step called "online setting". The sniffing
> characteristic must be configured before the online setting of the
> device, since NTA-specific initialization steps are necessary. At that
> point of time we cannot make use of ethtool, because the network
> interface name is not known yet. That means switching to your proposed
> ethtool-based configuration mechanism for HS NTA would result in an
> additional major rework of qeth device setup.

If you have a place to stick sysfs nodes, you've obviously
instantiated the device already.
--
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