From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934918AbaGYR1S (ORCPT ); Fri, 25 Jul 2014 13:27:18 -0400 Received: from mail-wi0-f176.google.com ([209.85.212.176]:45431 "EHLO mail-wi0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932839AbaGYR1Q (ORCPT ); Fri, 25 Jul 2014 13:27:16 -0400 MIME-Version: 1.0 In-Reply-To: References: <1406275499-7822-1-git-send-email-ast@plumgrid.com> <53D23EAF.4000001@redhat.com> <20140725115414.GA4770@salvia> Date: Fri, 25 Jul 2014 10:27:14 -0700 Message-ID: Subject: Re: [PATCH net-next] net: filter: rename 'struct sk_filter' to 'struct bpf_prog' From: Alexei Starovoitov To: Willem de Bruijn Cc: Pablo Neira Ayuso , Daniel Borkmann , "David S. Miller" , Network Development , linux-kernel , netfilter-devel Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jul 25, 2014 at 6:53 AM, Willem de Bruijn wrote: >>> >alternative fix for xt_bpf.h could be to replace: >>> > /* only used in the kernel */ >>> > struct sk_filter *filter __attribute__((aligned(8))); >>> >with >>> > /* only used in the kernel */ >>> > void *filter __attribute__((aligned(8))); >>> > >>> >but this 'void *' approach may further break broken userspace, >>> >whereas the fix implemented here is more seamless. >>> >>> Yep, that's not good, 'struct sk_filter' should never have been in a uapi >>> file actually. > > This follows a convention in include/uapi/linux/netfilter/*.h that > likely predates the introduction of uapi. A search for "Used > internally by the kernel" shows many more examples. I should not have > included filter.h, however. The common behavior when using pointers > to kernel-internal structures is to have a forward declaration. I suggest > making that change, instead of changing to void *. This avoids having > to add casts where xt_bpf_info is used in net/netfilter/xt_bpf.c: that will not avoid typecast. Either 'void *' approach or extra 'struct sk_filter;' approach, both need type casts to 'struct bpf_prog' in xt_bpf.c (because of SK_RUN_FILTER macro) Therefore I prefer extra 'struct sk_filter;' approach. > -#include > #include > > #define XT_BPF_MAX_NUM_INSTR 64 > > +struct sk_filter; > + > struct xt_bpf_info { > > I can send this as a separate patch to net-next, if that helps.