netdev - Re: [PATCH] Packet socket: mmapped IO: PACKET_TX

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:	Wed, 05 Nov 2008 12:02:21 +0100
From:	Patrick McHardy <kaber@...sh.net>
To:	Johann Baudy <johaahn@...il.com>
CC:	"Lovich, Vitali" <vlovich@...lcomm.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	Evgeniy Polyakov <zbr@...emap.net>
Subject: Re: [PATCH] Packet socket: mmapped IO: PACKET_TX_RING

Johann Baudy wrote:
> I would like to integrate this barrier mechanism in __packet_[set|
> get]_status() function. Thoughts?

The reason why its not in there is to avoid the unnecessary
barrier when setting up the ring in packet_set_ring().

The code is fishy though, I agree. Have a look at this discussion:

http://marc.info/?l=linux-netdev&m=119383985207984&w=2
--
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