On Wed, 2017-05-24 at 03:26 -0500, Eric W. Biederman wrote: > > So far no one has even bothered to seriously try the one solution that > is guaranteed to work because it takes a lot of changes to kernel code. > I believe the last effort snagged on what a pain it is to refactor the > user mode helper infrastructure. Yes, that's mostly true in my case although I wouldn't say I haven't looked at it seriously but equally I haven't got anything towards it yet either, sorry. I'm likely going to revisit this based on a couple of approaches. One is just what you describe and I had already been looking at this some time ago. It seems to me that adding a work queue type that starts and retains a process until the work queue is destroyed (similar to the way the work queue sub system starts a fail over thread for use under resource exhaustion) would be a sensible way to do it. This doesn't mean I think it's a good idea for reasons I've outlined in the past but the approach does warrant the effort to work out if it can be used without problems. And there's also the request key infrastructure which, as it is now, gets in the road of verifying results, *sigh*. Ian -- To unsubscribe from this list: send the line "unsubscribe cgroups" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
