Re: [PATCH 3.3] memcg: fix GPF when cgroup removal races with lastexit

[Konstantin Khlebnikov]

Konstantin Khlebnikov wrote:
> Hugh Dickins wrote:
> > Konstantin, I've not yet looked into how this patch affects your
> > patchsets; but I do know that this surreptitious-switch-to-root
> > behaviour seemed nightmarish when I was doing per-memcg per-zone
> > locking (particularly inside something like __activate_page(), where
> > we del and add under a single lock), and unnecessary once you and I
> > secure the memcg differently.  So you may just want to revert this in
> > patches for linux-next; but I've a suspicion that now we understand
> > it better, this technique might still be usable, and more efficient.
>
> Yes, something like that. But, I  must fix my "isolated-pages" counters first,
> otherwise I just reintroduce this bug again.

I have thought little more and invented better approach: we can keep isolated pages
counted in lruvec->lru_size[] and vmstat counters. Thus isolated pages will prevent
removing it's memory cgroup. This method is more complicated than your tricky pushing
pages to root lruvec, but it more generic and does not adds new page-counters.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/