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: Fri, 18 May 2012 08:22:31 -0700 From: Shirley Ma <mashirle@...ibm.com> To: Jason Wang <jasowang@...hat.com> Cc: eric.dumazet@...il.com, mst@...hat.com, netdev@...r.kernel.org, linux-kernel@...r.kernel.org, ebiederm@...ssion.com, davem@...emloft.net Subject: Re: [V2 PATCH 2/9] macvtap: zerocopy: fix truesize underestimation On Fri, 2012-05-18 at 18:10 +0800, Jason Wang wrote: > > On Thu, 2012-05-17 at 10:59 +0800, Jason Wang wrote: > >> Didn't see how this affact skb->len. And for truesize, I think they > >> are > >> different, when the offset were not zero, the data in this vector > >> were > >> divided into two parts. First part is copied into skb directly, and > >> the > >> second were pinned from a whole userspace page by > >> get_user_pages_fast(), > >> so we need count the whole page to the socket limit to prevent evil > >> application. > > What I meant that the code for skb->truesize has double added the > first > > offset if any left from that vector (partically copied into skb > > directly, and then count pagesize which includes the offset > (truesize += > > PAGE_SIZE)). > > Yes, I get you mean. There's no difference between first frag and > others: it's also possible for other frags that didn't occupy the > whole > page. Since we pin the whole user page, better to count the whole > page > size to prevent evil application. The difference between first frags and others is other frags might not occupy the whole page, but the first frags extra offset was doubled added in skb truesize. So it's ok for skb->truesize to be bigger than all the skb pinned pages here? Thanks Shirley -- 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