netdev - Re: [PATCH net-next 02/13] sk_buff: add skb extension infrastructure

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: <20181212.163832.2133855211032994962.davem@davemloft.net>
Date:   Wed, 12 Dec 2018 16:38:32 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     ssuryaextr@...il.com
Cc:     fw@...len.de, netdev@...r.kernel.org
Subject: Re: [PATCH net-next 02/13] sk_buff: add skb extension
 infrastructure

From: Stephen Suryaputra <ssuryaextr@...il.com>
Date: Wed, 12 Dec 2018 13:16:57 -0500

> On Mon, Dec 10, 2018 at 11:20 AM Florian Westphal <fw@...len.de> wrote:
> 
>> +#ifdef CONFIG_SKB_EXTENSIONS
>> +enum skb_ext_id {
>> +#if IS_ENABLED(CONFIG_BRIDGE_NETFILTER)
>> +       SKB_EXT_BRIDGE_NF,
>> +#endif
>> +       SKB_EXT_NUM, /* must be last */
>> +};
> 
> How about when proprietary extensions is desired? There are cases
> where our system has to pass special metadata from input to output in
> skbs.

Proprietary extensions will absolutely not be taken into consideration
when designing upstream features in the Linux kernel.