netdev - Re: [PATCH][next-next][v2] netlink: avoid to allocate full skb when sending to many devices

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]

Message-ID: <a9b4a4b9-04c4-bf55-3f08-b7889524374a@gmail.com>
Date:   Thu, 20 Sep 2018 06:43:32 -0700
From:   Eric Dumazet <eric.dumazet@...il.com>
To:     Li RongQing <lirongqing@...du.com>, netdev@...r.kernel.org
Subject: Re: [PATCH][next-next][v2] netlink: avoid to allocate full skb when
 sending to many devices



On 09/20/2018 01:54 AM, Li RongQing wrote:
> if skb->head is vmalloc address, when this skb is delivered, full
> allocation for this skb is required, if there are many devices,
> the full allocation will be called for every devices
> 
> now if it is vmalloc, allocate a new skb, whose data is not vmalloc
> address, and use new allocated skb to clone and send, to avoid to
> allocate full skb everytime.
> 
> Signed-off-by: Zhang Yu <zhangyu31@...du.com>
> Signed-off-by: Li RongQing <lirongqing@...du.com>


This looks a broken Signed-off-by chain to me.

Who really wrote this patch ?

Also, given that I gave feedback to your first version,
it is customary to CC me for future versions, unless you want me to not notice them.

And lastly this patch looks way too complicated to me.
You probably can write something much simpler.

Thanks.