netdev - Re: [Patch net-next] net: remove skb_sender_cpu

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: <CAM_iQpUtGbSnvV3Zi74Q5DsZBAAFGZyvjkkeBRciHxwTm4GCEg@mail.gmail.com>
Date:	Mon, 29 Feb 2016 10:55:11 -0800
From:	Cong Wang <xiyou.wangcong@...il.com>
To:	Daniel Borkmann <daniel@...earbox.net>
Cc:	Linux Kernel Network Developers <netdev@...r.kernel.org>,
	Eric Dumazet <edumazet@...gle.com>
Subject: Re: [Patch net-next] net: remove skb_sender_cpu_clear()

On Mon, Feb 29, 2016 at 10:50 AM, Daniel Borkmann <daniel@...earbox.net> wrote:
> On 02/28/2016 05:19 AM, Cong Wang wrote:
>>
>> After commit 52bd2d62ce67 ("net: better skb->sender_cpu and skb->napi_id
>> cohabitation")
>> skb_sender_cpu_clear() becomes empty and can be removed.
>>
>> Cc: Eric Dumazet <edumazet@...gle.com>
>> Signed-off-by: Cong Wang <xiyou.wangcong@...il.com>
>
>
> Wasn't the intention to keep this helper as a marker when packet
> crosses domains from RX to TX, see discussion here:
>
>   https://patchwork.ozlabs.org/patch/527167/
>
> Maybe better to rename it and add a comment into the helper to
> make the intention more clear?

Since when we need an empty function to mark some call path?
Isn't this supposed to be done by comments or documents?

BTW, I myself even don't think we need any comment, people
who touches it should understand it.