From: Willy Tarreau <w@1wt.eu>
To: John Stultz <johnstul@us.ibm.com>
Cc: stable@vger.kernel.org, Prarit Bhargava <prarit@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 00/11] 2.6.32-stable: Fix for leapsecond deadlock & hrtimer/futex issue
Date: Thu, 19 Jul 2012 14:56:53 +0200 [thread overview]
Message-ID: <20120719125653.GK16208@1wt.eu> (raw)
In-Reply-To: <20120719095311.GE16208@1wt.eu>
On Thu, Jul 19, 2012 at 11:53:11AM +0200, Willy Tarreau wrote:
> On Tue, Jul 17, 2012 at 05:34:30PM -0700, John Stultz wrote:
> > On 07/17/2012 03:05 PM, John Stultz wrote:
> > >This is the last backport I have ready at this time. I realize there's
> > >still the 2.6.27 tree, but if I recall correctly I had some trouble
> > >getting that booted in my test environment. I can take a swing at
> > >backporting it, but I may need a hand with testing.
> >
> > And if anyone is interested in helping test, I've got a first pass
> > (builds & mostly boots) of the 2.6.27-stable backports here:
> > git://git.linaro.org/people/jstultz/linux.git leapfix/2.6.27.62
> >
> > http://git.linaro.org/gitweb?p=people/jstultz/linux.git;a=shortlog;h=refs/heads/leapfix/2.6.27.62
> >
> > Unfortunately I run into udev issues trying to boot this on my more
> > recent test environment.
>
> John, don't waste your time trying to boot older kernels, I'm well
> equipped for this task and it's much easier for me, so let's split
> the work efficiently :-)
OK so first, I managed to crash latest 2.6.32.x in less than one minute
using leapcrash and I cannot crash it anymore after an hour with your
patches applied.
I'll try to develop a small futex-based PoC to test the other reproducer,
then I'll duplicate the tests on 2.6.27.
Looks good so far.
Thanks,
Willy
prev parent reply other threads:[~2012-07-19 12:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 22:05 [PATCH 00/11] 2.6.32-stable: Fix for leapsecond deadlock & hrtimer/futex issue John Stultz
2012-07-17 22:05 ` [PATCH 01/11] 2.6.32.x: ntp: Fix leap-second hrtimer livelock John Stultz
2012-07-17 22:05 ` [PATCH 02/11] 2.6.32.x: ntp: Correct TAI offset during leap second John Stultz
2012-07-17 22:05 ` [PATCH 03/11] 2.6.32.x: timekeeping: Fix CLOCK_MONOTONIC inconsistency during leapsecond John Stultz
2012-07-17 22:05 ` [PATCH 04/11] 2.6.32.x: time: Move common updates to a function John Stultz
2012-07-17 22:05 ` [PATCH 05/11] 2.6.32.x: hrtimer: Provide clock_was_set_delayed() John Stultz
2012-07-17 22:05 ` [PATCH 06/11] 2.6.32.x: timekeeping: Fix leapsecond triggered load spike issue John Stultz
2012-07-17 22:05 ` [PATCH 07/11] 2.6.32.x: timekeeping: Maintain ktime_t based offsets for hrtimers John Stultz
2012-07-17 22:05 ` [PATCH 08/11] 2.6.32.x: hrtimers: Move lock held region in hrtimer_interrupt() John Stultz
2012-07-17 22:05 ` [PATCH 09/11] 2.6.32.x: timekeeping: Provide hrtimer update function John Stultz
2012-07-17 22:05 ` [PATCH 10/11] 2.6.32.x: hrtimer: Update hrtimer base offsets each hrtimer_interrupt John Stultz
2012-07-17 22:05 ` [PATCH 11/11] 2.6.32.x: timekeeping: Add missing update call in timekeeping_resume() John Stultz
2012-07-18 0:34 ` [PATCH 00/11] 2.6.32-stable: Fix for leapsecond deadlock & hrtimer/futex issue John Stultz
2012-07-19 9:53 ` Willy Tarreau
2012-07-19 12:56 ` Willy Tarreau [this message]
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=20120719125653.GK16208@1wt.eu \
--to=w@1wt.eu \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=prarit@redhat.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
/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.