On Thu, Nov 9, 2023 at 1:36 PM Tejun Heo <tj@xxxxxxxxxx> wrote: > > Hello, > > On Sun, Oct 29, 2023 at 06:14:27AM +0000, Yafang Shao wrote: > > - [bpf_]task_get_cgroup1 > > Acquires the associated cgroup of a task within a specific cgroup1 > > hierarchy. The cgroup1 hierarchy is identified by its hierarchy ID. > > > > This new kfunc enables the tracing of tasks within a designated container > > or its ancestor cgroup directory in BPF programs. Additionally, it is > > capable of operating on named cgroups, providing valuable utility for > > hybrid cgroup mode scenarios. > > Sans minor nits, the whole series looks good to me. I can take the cgroup > prep patches through cgroup tree but it's also fine to route them through > the bpf tree with the rest of the series. Please let me know how folks want > to route the series once the minor issues are addressed. Do you think there could be conflicts between cgroup and bpf trees ? If so, maybe you can push the cgroup patches into the stable branch and pull it into the main cgroup branch and we'll pull the same branch into bpf-next. This way all shas will remain and no conflicts during the merge window.
