I update the bug title to better match what we're seeing.
The oops from the description is indeed just a timeout from some user space task that's stuck on clone().
So it looks like there's something wrong either in the cleanup code when flushing a network namespace (when the last process in the namespace dies) or something wrong with the refcount.
I update the bug title to better match what we're seeing.
The oops from the description is indeed just a timeout from some user space task that's stuck on clone().
So it looks like there's something wrong either in the cleanup code when flushing a network namespace (when the last process in the namespace dies) or something wrong with the refcount.