diff options
| author | Daniel Borkmann <dborkman@redhat.com> | 2014-05-23 18:43:58 +0200 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2014-05-23 16:48:05 -0400 |
| commit | b1fcd35cf53553a0a3ef949b05106d921446abc3 (patch) | |
| tree | 4784eb248a9705f2eae7dcb10968497f0559499f /net/core/ptp_classifier.c | |
| parent | 8556ce79d5986a87fee4c29300b4efee07c0f15e (diff) | |
| download | linux-stable-b1fcd35cf53553a0a3ef949b05106d921446abc3.tar.gz linux-stable-b1fcd35cf53553a0a3ef949b05106d921446abc3.tar.bz2 linux-stable-b1fcd35cf53553a0a3ef949b05106d921446abc3.zip | |
net: filter: let unattached filters use sock_fprog_kern
The sk_unattached_filter_create() API is used by BPF filters that
are not directly attached or related to sockets, and are used in
team, ptp, xt_bpf, cls_bpf, etc. As such all users do their own
internal managment of obtaining filter blocks and thus already
have them in kernel memory and set up before calling into
sk_unattached_filter_create(). As a result, due to __user annotation
in sock_fprog, sparse triggers false positives (incorrect type in
assignment [different address space]) when filters are set up before
passing them to sk_unattached_filter_create(). Therefore, let
sk_unattached_filter_create() API use sock_fprog_kern to overcome
this issue.
Signed-off-by: Daniel Borkmann <dborkman@redhat.com>
Acked-by: Alexei Starovoitov <ast@plumgrid.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/core/ptp_classifier.c')
| -rw-r--r-- | net/core/ptp_classifier.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/net/core/ptp_classifier.c b/net/core/ptp_classifier.c index 37d86157b76e..d3027a73fd4b 100644 --- a/net/core/ptp_classifier.c +++ b/net/core/ptp_classifier.c @@ -133,7 +133,7 @@ void __init ptp_classifier_init(void) { 0x16, 0, 0, 0x00000000 }, { 0x06, 0, 0, 0x00000000 }, }; - struct sock_fprog ptp_prog = { + struct sock_fprog_kern ptp_prog = { .len = ARRAY_SIZE(ptp_filter), .filter = ptp_filter, }; |