Re: memcg creates an unkillable task in 3.11-rc2

[Eric W. Biederman]

Michal Hocko <mhocko@xxxxxxx> writes:

> It seems that this one fell though the cracks?

Not completely, but it happened just as I was doing my initial triage of
memcg problems and I haven't quite made it back to this.

I have an even nastier memcg hang (without yet an easy reproducer).
During mkdir ext3 can add a page to the page cache with the ext3 journal
transaction lock held.  Normally that isn't a problem but freezing there
stops all writes to that filesystem, and the world stops.

It looks like the only way to avoid that kind of scenario is to move the
the memcg sleep to the edge of userspace, like we do with signals and a
few other things so we can be guaranteed not to increase lock hold
times, when it is avoidable.  I think I saw some similar comments about
the slab limiting.

Eric
--
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/