Al Viro wrote:
> On Mon, Feb 09, 2009 at 12:40:46AM -0800, Andrew Morton wrote:
>>> Thread 1:
>>> for ((; ;))
>>> {
>>> mount -t cgroup -o cpuset xxx /mnt > /dev/null 2>&1
>>> mkdir /mnt/0 > /dev/null 2>&1
>>> rmdir /mnt/0 > /dev/null 2>&1
>>> umount /mnt > /dev/null 2>&1
>>> }
>>>
>>> Thread 2:
>>> {
>>> mount -t cpuset xxx /mnt > /dev/null 2>&1
>>> umount /mnt > /dev/null 2>&1
>>> }
>
> How cute... Same mountpoint in both, so these mount(2) will sometimes
> fail (cgroup picks the same sb on the same options, AFAICS) and fail
> silently due to these redirects...
>
> That's a lovely way to stress-test a large part of ro-bind stuff *and*
> umount()-related code. Could you do C equivalent of the above (just
> the same syscalls in loop, nothing fancier) and do time-stamped strace?
>
Sure, I'll write a C version and try to reproduce the warning.
_______________________________________________
Containers mailing list
contain...@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/containers
_______________________________________________
Devel mailing list
Devel@openvz.org
https://openvz.org/mailman/listinfo/devel
