Re: [PATCH 00/11] 3.2-stable: Fix for leapsecond causedhrtimer/futex issue

From: Christoph Biedl
Date: Thu Jul 19 2012 - 16:56:59 EST


John Stultz wrote...

> Attached is the test case I used to reproduce and test the solution
> to the hard-hang deadlock.

I was wondering whether anybody managed to crash a virtualbox guest
using your program. No avail, using version 4.1.18 on the host and the
guest kernel running several 3.0.x (x < 38) kernels on both x32 and
x64, the guest utilies were stopped. Rather a fun fact I guess but I
wanted to let you know.

All real hardware tested, including a dockstar on armel, crashed as
predicted, while 3.0.38-rc1 was immune.

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