From: Daniel Borkmann <dborkman@redhat•com>
To: David Miller <davem@davemloft•net>
Cc: ast@plumgrid•com, netdev@vger•kernel.org
Subject: Re: [PATCH net-next v2 3/5] net: filter: get rid of sock_fprog_kern
Date: Fri, 25 Apr 2014 09:58:31 +0200 [thread overview]
Message-ID: <535A15A7.7080306@redhat.com> (raw)
In-Reply-To: <20140424.160237.1682834218902091375.davem@davemloft.net>
On 04/24/2014 10:02 PM, David Miller wrote:
...
> It's so that we can always have the correct type for the pointers, and
> we can show cleanly (without lots of ugly casts) to sparse that whether
> we expect a pointer to be a user or a kernel one.
Understood, I'll take the time to go the other way around and try to
convert sk_unattached_filter_create() API to use struct sock_fprog_kern
instead as this is only for in-kernel users.
next prev parent reply other threads:[~2014-04-25 7:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 6:45 [PATCH net-next v2 0/5] BPF updates Daniel Borkmann
2014-04-24 6:45 ` [PATCH net-next v2 1/5] net: filter: simplify label names from jump-table Daniel Borkmann
2014-04-24 6:45 ` [PATCH net-next v2 2/5] net: filter: misc/various cleanups Daniel Borkmann
2014-04-24 20:00 ` David Miller
2014-04-25 7:52 ` Daniel Borkmann
2014-04-24 6:45 ` [PATCH net-next v2 3/5] net: filter: get rid of sock_fprog_kern Daniel Borkmann
2014-04-24 20:02 ` David Miller
2014-04-25 7:58 ` Daniel Borkmann [this message]
2014-04-24 6:45 ` [PATCH net-next v2 4/5] net: filter: make register namings more comprehensible Daniel Borkmann
2014-04-24 6:45 ` [PATCH net-next v2 5/5] net: filter: optimize BPF migration for ARG1/CTX handling Daniel Borkmann
2014-04-24 15:43 ` Alexei Starovoitov
2014-04-24 20:04 ` David Miller
2014-04-26 18:06 ` Alexei Starovoitov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=535A15A7.7080306@redhat.com \
--to=dborkman@redhat$(echo .)com \
--cc=ast@plumgrid$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox