From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexei Starovoitov Subject: Re: [PATCH v2 net-next 2/4] net: add skeleton of bpfilter kernel module Date: Fri, 4 May 2018 18:00:58 -0700 Message-ID: <20180505010056.are63gsmf7yrlxpe@ast-mbp> References: <20180503043604.1604587-1-ast@kernel.org> <20180503043604.1604587-3-ast@kernel.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: Alexei Starovoitov , davem@davemloft.net, daniel@iogearbox.net, torvalds@linux-foundation.org, gregkh@linuxfoundation.org, luto@amacapital.net, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, kernel-team@fb.com To: Edward Cree Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Thu, May 03, 2018 at 03:23:55PM +0100, Edward Cree wrote: > On 03/05/18 05:36, Alexei Starovoitov wrote: > > bpfilter.ko consists of bpfilter_kern.c (normal kernel module code) > > and user mode helper code that is embedded into bpfilter.ko > > > > The steps to build bpfilter.ko are the following: > > - main.c is compiled by HOSTCC into the bpfilter_umh elf executable file > > - with quite a bit of objcopy and Makefile magic the bpfilter_umh elf file > > is converted into bpfilter_umh.o object file > > with _binary_net_bpfilter_bpfilter_umh_start and _end symbols > > Example: > > $ nm ./bld_x64/net/bpfilter/bpfilter_umh.o > > 0000000000004cf8 T _binary_net_bpfilter_bpfilter_umh_end > > 0000000000004cf8 A _binary_net_bpfilter_bpfilter_umh_size > > 0000000000000000 T _binary_net_bpfilter_bpfilter_umh_start > > - bpfilter_umh.o and bpfilter_kern.o are linked together into bpfilter.ko > > > > bpfilter_kern.c is a normal kernel module code that calls > > the fork_usermode_blob() helper to execute part of its own data > > as a user mode process. > > > > Notice that _binary_net_bpfilter_bpfilter_umh_start - end > > is placed into .init.rodata section, so it's freed as soon as __init > > function of bpfilter.ko is finished. > > As part of __init the bpfilter.ko does first request/reply action > > via two unix pipe provided by fork_usermode_blob() helper to > > make sure that umh is healthy. If not it will kill it via pid. > > > > Later bpfilter_process_sockopt() will be called from bpfilter hooks > > in get/setsockopt() to pass iptable commands into umh via bpfilter.ko > > > > If admin does 'rmmod bpfilter' the __exit code bpfilter.ko will > > kill umh as well. > > > > Signed-off-by: Alexei Starovoitov ... > > +static void stop_umh(void) > > +{ > > + if (bpfilter_process_sockopt) { > I worry about locking here.  Is it possible for two calls to >  bpfilter_process_sockopt() to run in parallel, both fail, and thus both >  call stop_umh()?  And if both end up calling shutdown_umh(), we double >  fput(). I thought iptables sockopt is serialized earlier. Nope. We need to grab the mutex to access these pipes. Will fix. Thanks for spelling nits. Will fix as well.