| 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: <20150218210830.GA7778@localhost.localdomain> Date: Wed, 18 Feb 2015 22:08:30 +0100 From: Richard Cochran <richardcochran@...il.com> To: Stathis Voukelatos <stathis.voukelatos@...n.co.uk> Cc: linux-kernel@...r.kernel.org, devicetree@...r.kernel.org, netdev@...r.kernel.org, abrestic@...omium.org Subject: Re: [PATCH v2 0/3] net: Linn Ethernet Packet Sniffer driver On Tue, Feb 17, 2015 at 02:03:30PM +0000, Stathis Voukelatos wrote: > The command string for packet matching is stored in module RAM > and consists of a sequence of 16-bit entries. Each entry includes > an 8-bit command code and and 8-bit data value. Valid command > codes are: > 0 - Don't care > 1 - Match: packet data must match command string byte > 2 - Copy: packet data will be copied to FIFO > 3 - Match/Stamp: if packet data matches string byte, a timestamp > is copied into the FIFO > 4 - Copy/Done: packet data will be copied into the FIFO. > This command terminates the command string. Why do you need to expose this interface to user space at all? Why not just time stamp every frame? How does the "Match" command work? The frame must have one particular byte? That can't be right. Please explain. Thanks, Richard -- 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