On 12/1/06, Paul Jackson <[EMAIL PROTECTED]> wrote:
Read the comment in kernel/cpuset.c for the routine cpuset_destroy().
It explains that update_flag() is called where it is (turning off
the cpu_exclusive flag, if it was set), to avoid the calling sequence:
cpuset_destroy->update_flag->update
Paul M wrote:
> Ah - this may be the lockup that PaulJ hit.
Yes - looks like this fixes it. Thanks, Srivatsa.
And with that fix, it becomes obvious how to reproduce this problem:
mount -t cpuset cpuset /dev/cpuset # if not already mounted
cd /dev/cpuset
mkdir foo
On 12/1/06, Srivatsa Vaddagiri <[EMAIL PROTECTED]> wrote:
This patches fixes various bugs I hit in the recently posted container
patches.
1. If a subsystem registers with fork/exit hook during bootup (much
before rcu is initialized), then the resulting synchronize_rcu() in
container_regist
This patches fixes various bugs I hit in the recently posted container
patches.
1. If a subsystem registers with fork/exit hook during bootup (much
before rcu is initialized), then the resulting synchronize_rcu() in
container_register_subsys() hangs. Avoid this by not calling
synchroniz
4 matches
Mail list logo
