From: Christoph Biedl <linux-kernel.bfrz@manchmal.in-ulm.de>
To: John Stultz <johnstul@us.ibm.com>
Cc: stable@vger.kernel.org, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 00/11] 3.2-stable: Fix for leapsecond caused hrtimer/futex issue
Date: Thu, 19 Jul 2012 22:48:29 +0200 [thread overview]
Message-ID: <1342730535@msgid.manchmal.in-ulm.de> (raw)
In-Reply-To: <50050FD9.3070403@us.ibm.com>
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
next prev parent reply other threads:[~2012-07-19 20:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 7:05 [PATCH 00/11] 3.2-stable: Fix for leapsecond caused hrtimer/futex issue John Stultz
2012-07-17 7:05 ` [PATCH 01/11] 3.2.x: ntp: Fix leap-second hrtimer livelock John Stultz
2012-07-17 7:05 ` [PATCH 02/11] 3.2.x: ntp: Correct TAI offset during leap second John Stultz
2012-07-17 7:05 ` [PATCH 03/11] 3.2.x: timekeeping: Fix CLOCK_MONOTONIC inconsistency during leapsecond John Stultz
2012-07-17 7:05 ` [PATCH 04/11] 3.2.x: time: Move common updates to a function John Stultz
2012-07-17 7:05 ` [PATCH 05/11] 3.2.x: hrtimer: Provide clock_was_set_delayed() John Stultz
2012-07-17 7:05 ` [PATCH 06/11] 3.2.x: timekeeping: Fix leapsecond triggered load spike issue John Stultz
2012-07-17 7:05 ` [PATCH 07/11] 3.2.x: timekeeping: Maintain ktime_t based offsets for hrtimers John Stultz
2012-07-17 7:05 ` [PATCH 08/11] 3.2.x: hrtimers: Move lock held region in hrtimer_interrupt() John Stultz
2012-07-17 7:05 ` [PATCH 09/11] 3.2.x: timekeeping: Provide hrtimer update function John Stultz
2012-07-17 7:05 ` [PATCH 10/11] 3.2.x: hrtimer: Update hrtimer base offsets each hrtimer_interrupt John Stultz
2012-07-17 7:05 ` [PATCH 11/11] 3.2.x: timekeeping: Add missing update call in timekeeping_resume() John Stultz
2012-07-17 7:10 ` [PATCH 00/11] 3.2-stable: Fix for leapsecond caused hrtimer/futex issue John Stultz
2012-07-19 20:48 ` Christoph Biedl [this message]
2012-07-23 19:51 ` John Stultz
2012-07-24 2:37 ` Ben Hutchings
2012-07-22 18:50 ` Ben Hutchings
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1342730535@msgid.manchmal.in-ulm.de \
--to=linux-kernel.bfrz@manchmal.in-ulm.de \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.