From: David Miller <davem@davemloft.net>
To: daniel@iogearbox.net
Cc: netdev@vger.kernel.org
Subject: Re: more bpf samples build breakage...
Date: Mon, 01 May 2017 16:45:26 -0400 (EDT) [thread overview]
Message-ID: <20170501.164526.2280829777190467409.davem@davemloft.net> (raw)
In-Reply-To: <59079CE2.6010305@iogearbox.net>
From: Daniel Borkmann <daniel@iogearbox.net>
Date: Mon, 01 May 2017 22:38:58 +0200
> BPF samples:
>
> [root@apoc bpf]# make > /dev/null
> In file included from
> /root/cilium/net-next/samples/bpf/cookie_uid_helper_example.c:54:0:
> /root/cilium/net-next/samples/bpf/cookie_uid_helper_example.c: In
> function ‘prog_load’:
> /root/cilium/net-next/samples/bpf/cookie_uid_helper_example.c:119:5:
> warning: overflow in implicit constant conversion [-Woverflow]
> -32 + offsetof(struct stats, uid)),
> ^
> /root/cilium/net-next/samples/bpf/libbpf.h:135:12: note: in definition
> of macro ‘BPF_STX_MEM’
> .off = OFF, \
> ^
> /root/cilium/net-next/samples/bpf/cookie_uid_helper_example.c:121:5:
> warning: overflow in implicit constant conversion [-Woverflow]
> -32 + offsetof(struct stats, packets), 1),
> ^
> /root/cilium/net-next/samples/bpf/libbpf.h:155:12: note: in definition
> of macro ‘BPF_ST_MEM’
> .off = OFF, \
> ^
> /root/cilium/net-next/samples/bpf/cookie_uid_helper_example.c:129:5:
> warning: overflow in implicit constant conversion [-Woverflow]
> -32 + offsetof(struct stats, bytes)),
> ^
> /root/cilium/net-next/samples/bpf/libbpf.h:135:12: note: in definition
> of macro ‘BPF_STX_MEM’
> .off = OFF, \
> ^
> [root@apoc bpf]#
>
> Above warning is from 51570a5ab2b7 ("A Sample of using socket
> cookie and uid for traffic monitoring"). I can see to send a
> fix for it.
Please do, thanks.
prev parent reply other threads:[~2017-05-01 20:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-01 19:30 more bpf samples build breakage David Miller
2017-05-01 19:44 ` David Miller
2017-05-01 20:38 ` Daniel Borkmann
2017-05-01 20:45 ` David Miller [this message]
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=20170501.164526.2280829777190467409.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=daniel@iogearbox.net \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.