netdev - Re: [PATCH net-next] selftests: net: add PF

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

Message-Id: <20130407.170243.1891515530961395735.davem@davemloft.net>
Date:	Sun, 07 Apr 2013 17:02:43 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	dborkman@...hat.com
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH net-next] selftests: net: add PF_PACKET TPACKET
 v1/v2/v3 selftests

From: Daniel Borkmann <dborkman@...hat.com>
Date: Wed,  3 Apr 2013 01:00:51 +0200

> This patch adds a simple test case that probes the packet socket's
> TPACKET_V1, TPACKET_V2 and TPACKET_V3 behavior regarding mmap(2)'ed
> I/O for a small burst of 100 packets. The test currently runs for ...
> 
>   TPACKET_V1: RX_RING, TX_RING
>   TPACKET_V2: RX_RING, TX_RING
>   TPACKET_V3: RX_RING
> 
> ... and will output on success:
> 
>   test: TPACKET_V1 with PACKET_RX_RING .................... 100 pkts (9600 bytes)
>   test: TPACKET_V1 with PACKET_TX_RING .................... 100 pkts (9600 bytes)
>   test: TPACKET_V2 with PACKET_RX_RING .................... 100 pkts (9600 bytes)
>   test: TPACKET_V2 with PACKET_TX_RING .................... 100 pkts (9600 bytes)
>   test: TPACKET_V3 with PACKET_RX_RING .................... 100 pkts (9600 bytes)
>   OK. All tests passed
> 
> Reusable parts of psock_fanout.c have been put into a psock_lib.h
> file for common usage. Test case successfully tested on x86_64.
> 
> Signed-off-by: Daniel Borkmann <dborkman@...hat.com>

Applied, thanks!
--
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