| 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
| ||
|
Date: Sun, 26 Sep 2010 18:25:48 -0700 (PDT) From: David Miller <davem@...emloft.net> To: eric.dumazet@...il.com Cc: jarkao2@...il.com, xiaosuo@...il.com, socketcan@...tkopp.net, mst@...hat.com, netdev@...r.kernel.org Subject: Re: [PATCH v3] net: af_packet: don't call tpacket_destruct_skb() until the skb is sent out From: Eric Dumazet <eric.dumazet@...il.com> Date: Fri, 24 Sep 2010 09:01:00 +0200 > af_packet (tx with mmap) is broken. I wonder who really uses it ? I suspect now that af_packet supports VNET headers on transmit, there are some things using this tx+mmap thing for sure. > To properly cope with paged skbs, it should not try to fit several > packets per page. > > The mmap api should change so that one mmaped page belongs to at most > one skb, or else we need invasive changes in net/core > > This probably makes this stuff less interesting, unless the need is to > send big packets. In this case, why splice was not used instead of > custom mmap ? I don't really see what the big issue is. When the data destructor runs it means that packet's part of the pages are available for reuse for the tx mmap client. And if I read it correctly, that's exactly what tpacket_destruct_skb() is in fact doing. There seems to be no conflict with that rule and reusing a page for multiple packets. -- 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
Powered by blists - more mailing lists