On Mon, May 30, 2022 at 02:17:11PM -0700, Andrew Morton wrote: > On Mon, 30 May 2022 15:49:08 +0800 Muchun Song <songmuchun@xxxxxxxxxxxxx> wrote: > > > This version is rebased on v5.18. > > Not a great choice of base, really. mm-stable or mm-unstable or > linux-next or even linus-of-the-day are all much more up to date. > I'll rebase it to linux-next in v6. > Although the memcg reviewer tags are pretty thin, I was going to give > it a run. But after fixing a bunch of conflicts I got about halfway > through then gave up on a big snarl in get_obj_cgroup_from_current(). > Got it. Will fix. > > RFC v1: https://lore.kernel.org/all/20210330101531.82752-1-songmuchun@xxxxxxxxxxxxx/ > > Surprising, that was over a year ago. Why has is taken so long? > Yeah, a little long. This issue has been going on for years. I have proposed an approach based on objcg to solve this issue last year, however, we are not sure if this is the best choice. So this patchset stalled for months. Recently, this issue was proposed in LSFMM 2022 conference by Roman, consensus was that the objcg-based reparenting is fine as well. So this patchset has recently resumed. Thanks.
