From: Hao Luo <haoluo@google.com>
To: linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
netdev@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>, Yonghong Song <yhs@fb.com>,
KP Singh <kpsingh@kernel.org>,
John Fastabend <john.fastabend@gmail.com>,
Jiri Olsa <jolsa@kernel.org>, Stanislav Fomichev <sdf@google.com>,
Yosry Ahmed <yosryahmed@google.com>, Hao Luo <haoluo@google.com>
Subject: [PATCH bpf-next 0/2] Add CGROUP prefix to cgroup_iter_order
Date: Thu, 25 Aug 2022 14:39:03 -0700 [thread overview]
Message-ID: <20220825213905.1817722-1-haoluo@google.com> (raw)
As suggested by Andrii, add 'CGROUP' to cgroup_iter_order. This fix is
divided into two patches. Patch 1/2 fixes the commit that introduced
cgroup_iter. Patch 2/2 fixes the selftest that uses the
cgroup_iter_order. This is because the selftest was introduced in a
different commit. I tested this patchset via the following command:
test_progs -t cgroup,iter,btf_dump
Hao Luo (2):
bpf: Add CGROUP to cgroup_iter order
selftests/bpf: Fix test that uses cgroup_iter order
include/uapi/linux/bpf.h | 10 +++---
kernel/bpf/cgroup_iter.c | 32 +++++++++----------
tools/include/uapi/linux/bpf.h | 10 +++---
.../selftests/bpf/prog_tests/btf_dump.c | 2 +-
.../prog_tests/cgroup_hierarchical_stats.c | 2 +-
.../selftests/bpf/prog_tests/cgroup_iter.c | 10 +++---
6 files changed, 33 insertions(+), 33 deletions(-)
--
2.37.2.672.g94769d06f0-goog
next reply other threads:[~2022-08-25 21:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 21:39 Hao Luo [this message]
2022-08-25 21:39 ` [PATCH bpf-next 1/2] bpf: Add CGROUP to cgroup_iter order Hao Luo
2022-08-25 21:39 ` [PATCH bpf-next 2/2] selftests/bpf: Fix test that uses " Hao Luo
2022-08-25 21:56 ` [PATCH bpf-next 0/2] Add CGROUP prefix to cgroup_iter_order Andrii Nakryiko
2022-08-25 22:00 ` Hao Luo
2022-08-25 23:19 ` Yosry Ahmed
2022-08-26 2:03 ` Andrii Nakryiko
2022-08-26 2:04 ` Yosry Ahmed
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=20220825213905.1817722-1-haoluo@google.com \
--to=haoluo@google.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=yhs@fb.com \
--cc=yosryahmed@google.com \
/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