linux-kernel - Re: [net-next PATCH 3/5] net: Introduce SO_INCOMING_NAPI

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: <1489703227.28631.253.camel@edumazet-glaptop3.roam.corp.google.com>
Date:   Thu, 16 Mar 2017 15:27:07 -0700
From:   Eric Dumazet <eric.dumazet@...il.com>
To:     Alexander Duyck <alexander.duyck@...il.com>
Cc:     netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
        sridhar.samudrala@...el.com, edumazet@...gle.com,
        davem@...emloft.net
Subject: Re: [net-next PATCH 3/5] net: Introduce SO_INCOMING_NAPI_ID

On Thu, 2017-03-16 at 11:32 -0700, Alexander Duyck wrote:

>  
> +	case SO_INCOMING_NAPI_ID:
> +		v.val = sk->sk_napi_id;
> +		break;

I guess that here you should filter invalid values.

(So that you no longer need the first patch in this series)

Also, it looks like eBPF will need to get access to skb->napi_id for
efficient SO_REUSEPORT support ?

Thanks.