From: Kui-Feng Lee <kuifeng@fb.com>
To: "olsajiri@gmail.com" <olsajiri@gmail.com>
Cc: "daniel@iogearbox.net" <daniel@iogearbox.net>,
Kernel Team <Kernel-team@fb.com>, Yonghong Song <yhs@fb.com>,
"ast@kernel.org" <ast@kernel.org>,
"andrii@kernel.org" <andrii@kernel.org>,
"bpf@vger.kernel.org" <bpf@vger.kernel.org>
Subject: Re: [PATCH bpf-next v5 1/3] bpf: Parameterize task iterators.
Date: Tue, 16 Aug 2022 17:21:03 +0000 [thread overview]
Message-ID: <7467b1e10b2693d037184559927a281488c25f5b.camel@fb.com> (raw)
In-Reply-To: <YvlaCMB6DRIu1vjI@krava>
On Sun, 2022-08-14 at 22:24 +0200, Jiri Olsa wrote:
> On Wed, Aug 10, 2022 at 05:16:52PM -0700, Kui-Feng Lee wrote:
>
> SNIP
>
> > +static int bpf_iter_attach_task(struct bpf_prog *prog,
> > + union bpf_iter_link_info *linfo,
> > + struct bpf_iter_aux_info *aux)
> > +{
> > + unsigned int flags;
> > + struct pid_namespace *ns;
> > + struct pid *pid;
> > + pid_t tgid;
> > +
> > + if (linfo->task.tid != 0) {
> > + aux->task.type = BPF_TASK_ITER_TID;
> > + aux->task.tid = linfo->task.tid;
> > + } else if (linfo->task.tgid != 0) {
> > + aux->task.type = BPF_TASK_ITER_TGID;
> > + aux->task.tgid = linfo->task.tgid;
> > + } else if (linfo->task.pid_fd != 0) {
> > + aux->task.type = BPF_TASK_ITER_TGID;
> > + pid = pidfd_get_pid(linfo->task.pid_fd, &flags);
> > + if (IS_ERR(pid))
> > + return PTR_ERR(pid);
> > +
> > + ns = task_active_pid_ns(current);
> > + if (IS_ERR(ns))
> > + return PTR_ERR(ns);
> > +
> > + tgid = pid_nr_ns(pid, ns);
> > + if (tgid <= 0)
> > + return -EINVAL;
> > +
> > + aux->task.tgid = tgid;
> > + } else {
> > + aux->task.type = BPF_TASK_ITER_ALL;
> > + }
> > +
> > + return 0;
> > +}
> > +
> > static const struct seq_operations task_seq_ops = {
> > .start = task_seq_start,
> > .next = task_seq_next,
> > @@ -137,8 +198,7 @@ struct bpf_iter_seq_task_file_info {
> > static struct file *
> > task_file_seq_get_next(struct bpf_iter_seq_task_file_info *info)
> > {
> > - struct pid_namespace *ns = info->common.ns;
> > - u32 curr_tid = info->tid;
> > + u32 saved_tid = info->tid;
>
> we use 'curr_' prefix for other stuff in the function, like
> curr_task, curr_fd .. I think we should either change all of
> them or actually keep curr_tid, which seem better to me
The purpose of the variable is changed, so I think 'curr_tid' is not
feasible anymore. It was the tid of the task that we are visiting.
But, now, it is the tid of the task that the iterator was visiting
when/before entering the function. In this patch, info->tid is always
the value of the current visiting task.
>
> jirka
>
> > struct task_struct *curr_task;
> > unsigned int curr_fd = info->fd;
> >
> > @@ -151,21 +211,18 @@ task_file_seq_get_next(struct
> > bpf_iter_seq_task_file_info *info)
> > curr_task = info->task;
> > curr_fd = info->fd;
> > } else {
> > - curr_task = task_seq_get_next(ns, &curr_tid,
> > true);
> > + curr_task = task_seq_get_next(&info->common, &info-
> > >tid, true);
> > if (!curr_task) {
> > info->task = NULL;
> > - info->tid = curr_tid;
> > return NULL;
> > }
> >
> > - /* set info->task and info->tid */
> > + /* set info->task */
> > info->task = curr_task;
> > - if (curr_tid == info->tid) {
> > + if (saved_tid == info->tid)
> > curr_fd = info->fd;
> > - } else {
> > - info->tid = curr_tid;
> > + else
> > curr_fd = 0;
> > - }
> > }
> >
>
> SNIP
next prev parent reply other threads:[~2022-08-16 17:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 0:16 [PATCH bpf-next v5 0/3] Parameterize task iterators Kui-Feng Lee
2022-08-11 0:16 ` [PATCH bpf-next v5 1/3] bpf: " Kui-Feng Lee
2022-08-13 22:17 ` Yonghong Song
2022-08-15 1:01 ` Alexei Starovoitov
2022-08-16 4:42 ` Andrii Nakryiko
2022-08-18 3:40 ` Yonghong Song
2022-08-16 5:25 ` Andrii Nakryiko
2022-08-18 4:31 ` Yonghong Song
2022-08-25 17:50 ` Andrii Nakryiko
2022-08-16 17:00 ` Kui-Feng Lee
2022-08-14 20:24 ` Jiri Olsa
2022-08-16 17:21 ` Kui-Feng Lee [this message]
2022-08-15 23:08 ` Hao Luo
2022-08-16 19:11 ` Kui-Feng Lee
2022-08-16 5:02 ` Andrii Nakryiko
2022-08-16 18:45 ` Kui-Feng Lee
2022-08-11 0:16 ` [PATCH bpf-next v5 2/3] bpf: Handle bpf_link_info for the parameterized task BPF iterators Kui-Feng Lee
2022-08-13 22:23 ` Yonghong Song
2022-08-11 0:16 ` [PATCH bpf-next v5 3/3] selftests/bpf: Test " Kui-Feng Lee
2022-08-13 22:50 ` Yonghong Song
2022-08-18 17:24 ` Kui-Feng Lee
2022-08-16 5:15 ` Andrii Nakryiko
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=7467b1e10b2693d037184559927a281488c25f5b.camel@fb.com \
--to=kuifeng@fb.com \
--cc=Kernel-team@fb.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=olsajiri@gmail.com \
--cc=yhs@fb.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;
as well as URLs for NNTP newsgroup(s).