[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CACYkzJ4xmJBtHBbRfDRnmrCLw=NTf6tYSYXDS6==57RMeBz-4Q@mail.gmail.com>
Date: Fri, 14 May 2021 13:21:41 +0200
From: KP Singh <kpsingh@...nel.org>
To: Alexei Starovoitov <alexei.starovoitov@...il.com>
Cc: xufeng zhang <yunbo.xufeng@...ux.alibaba.com>,
Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
bpf <bpf@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org>,
LSM List <linux-security-module@...r.kernel.org>,
Florent Revest <revest@...omium.org>,
Brendan Jackman <jackmanb@...omium.org>,
Yonghong Song <yhs@...com>, Song Liu <songliubraving@...com>,
Martin KaFai Lau <kafai@...com>,
John Fastabend <john.fastabend@...il.com>,
Joe Stringer <joe@...ium.io>,
Quentin Monnet <quentin@...valent.com>
Subject: Re: [RFC] [PATCH bpf-next 1/1] bpf: Add a BPF helper for getting the
cgroup path of current task
> > About your suggestion, the *cgroup_id helpers only works for cgroup v2,
> > however, we're still using cgroup v1 in product,and even for cgroup v2,
> > I'm not sure if there is any way for user space to get this cgroup id
> > timely(after container created, but before container start to run)。
> >
> > So if there is any effective way works for cgroup v1?
>
> https://github.com/systemd/systemd/blob/main/NEWS#L379
I agree that we should not focus on cgroup v1 if we do add a helper.
Powered by blists - more mailing lists