From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Wangnan (F)" Subject: Re: [PATCH net-next 1/6] bpf: introduce BPF_PROG_TEST_RUN command Date: Fri, 31 Mar 2017 11:12:23 +0800 Message-ID: <67b19080-26f9-67ac-d7fa-e621a90c54bb@huawei.com> References: <20170331013157.3298003-1-ast@fb.com> <20170331013157.3298003-2-ast@fb.com> <9105ab34-8fee-fab4-96fe-3bfe7f3a84b7@huawei.com> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Cc: Daniel Borkmann , Martin KaFai Lau , , To: Alexei Starovoitov , "David S . Miller" Return-path: Received: from szxga02-in.huawei.com ([45.249.212.188]:4865 "EHLO dggrg02-dlp.huawei.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1753338AbdCaDNi (ORCPT ); Thu, 30 Mar 2017 23:13:38 -0400 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On 2017/3/31 10:57, Alexei Starovoitov wrote: > On 3/30/17 7:53 PM, Wangnan (F) wrote: >> I suggest using a CONFIG option to enable/disable code in >> test_run.o to reduce attack plane. > > attack plane? what attack do you see and how config helps? > I think all testing features are not required to be compiled for a production system. A feature which should never be used looks dangerous to me. I suggest adding a CONFIG option like CONFIG_BPF_PROGRAM_TEST_RUN to control whether the kernel should be compiled with this feature or not. We can enable by default, and give people a chance to turn it off. At least in my company people tends to turn all unneeded features off. If you don't provide a config option they will make one by themselves. Thank you.