From: "Iago López Galeiras" <iago@kinvolk.io>
To: john.fastabend@gmail.com, ast@kernel.org, daniel@iogearbox.net
Cc: alban@kinvolk.io, krzesimir@kinvolk.io, bpf@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH bpf-next v4 2/4] bpf: sync bpf.h to tools/ for bpf_sock_ops->netns*
Date: Fri, 24 May 2019 17:59:29 +0200 [thread overview]
Message-ID: <20190524155931.7946-3-iago@kinvolk.io> (raw)
In-Reply-To: <20190524155931.7946-1-iago@kinvolk.io>
From: Alban Crequy <alban@kinvolk.io>
The change in struct bpf_sock_ops is synchronised
from: include/uapi/linux/bpf.h
to: tools/include/uapi/linux/bpf.h
Signed-off-by: Alban Crequy <alban@kinvolk.io>
---
Changes since v2:
- standalone patch for the sync (requested by Y Song)
---
tools/include/uapi/linux/bpf.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tools/include/uapi/linux/bpf.h b/tools/include/uapi/linux/bpf.h
index 63e0cf66f01a..e64066a09a5f 100644
--- a/tools/include/uapi/linux/bpf.h
+++ b/tools/include/uapi/linux/bpf.h
@@ -3261,6 +3261,8 @@ struct bpf_sock_ops {
__u32 sk_txhash;
__u64 bytes_received;
__u64 bytes_acked;
+ __u64 netns_dev;
+ __u64 netns_ino;
};
/* Definitions for bpf_sock_ops_cb_flags */
--
2.21.0
next prev parent reply other threads:[~2019-05-24 16:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 15:59 [PATCH bpf-next v4 0/4] sock ops: add netns ino and dev in bpf context Iago López Galeiras
2019-05-24 15:59 ` [PATCH bpf-next v4 1/4] bpf: " Iago López Galeiras
2019-05-24 17:47 ` Y Song
2019-05-31 14:24 ` Iago López Galeiras
2019-05-24 15:59 ` Iago López Galeiras [this message]
2019-05-24 15:59 ` [PATCH bpf-next v4 3/4] selftests: bpf: read netns_ino from struct bpf_sock_ops Iago López Galeiras
2019-05-24 15:59 ` [PATCH bpf-next v4 4/4] selftests: bpf: verifier: read netns_dev and " Iago López Galeiras
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=20190524155931.7946-3-iago@kinvolk.io \
--to=iago@kinvolk.io \
--cc=alban@kinvolk.io \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=krzesimir@kinvolk.io \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®