netdev - Re: [PATCH,net-next,0/2] Improve code coverage of syzkaller

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] [day] [month] [year] [list]

Message-Id: <20170920.093646.2147747625061858821.davem@davemloft.net>
Date:   Wed, 20 Sep 2017 09:36:46 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     willemdebruijn.kernel@...il.com
Cc:     peterpenkov96@...il.com, netdev@...r.kernel.org
Subject: Re: [PATCH,net-next,0/2] Improve code coverage of syzkaller

From: Willem de Bruijn <willemdebruijn.kernel@...il.com>
Date: Wed, 20 Sep 2017 11:38:45 -0400

> I think that the compile time option was chosen because of the ns_capable
> check, so that with user namespaces unprivileged processes can control this
> path. Perhaps we can require capable() only to set IFF_NAPI_FRAGS.
> 
> Then we can convert the napi_gro_receive path to be conditional on a new
> IFF_NAPI flag instead of this compile time option.

That works for me.