lttng-dev.lists.lttng.org archive mirror
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: mingo@kernel.org, hpa@zytor.com, linux-kernel@vger.kernel.org,
	gerlando.falauto@keymile.com, john.stultz@linaro.org,
	minggr@gmail.com, tglx@linutronix.de
Cc: linux-tip-commits@vger.kernel.org, lttng-dev@lists.lttng.org
Subject: Re: [tip:timers/urgent] timekeeping: Fix HRTICK related deadlock from ntp lock changes
Date: Mon, 16 Sep 2013 12:04:26 -0400	[thread overview]
Message-ID: <20130916160426.GA24669@Krystal> (raw)
In-Reply-To: <tip-7bd36014460f793c19e7d6c94dab67b0afcfcb7f@git.kernel.org>

Hi Ingo,

Do you have an estimate of the time it will take for this fix to hit
mainline, stable-3.10 and stable-3.11 ? Meanwhile, I'm marking 3.10 and
3.11 as broken for LTTng with a kernel version at compile-time, since
this kernel regression currently triggers hard system lockup when people
use LTTng on those kernels, and this is certainly something nobody
wants.

Thanks,

Mathieu

* tip-bot for John Stultz (tipbot@zytor.com) wrote:
> Commit-ID:  7bd36014460f793c19e7d6c94dab67b0afcfcb7f
> Gitweb:     http://git.kernel.org/tip/7bd36014460f793c19e7d6c94dab67b0afcfcb7f
> Author:     John Stultz <john.stultz@linaro.org>
> AuthorDate: Wed, 11 Sep 2013 16:50:56 -0700
> Committer:  Ingo Molnar <mingo@kernel.org>
> CommitDate: Thu, 12 Sep 2013 07:49:51 +0200
> 
> timekeeping: Fix HRTICK related deadlock from ntp lock changes
> 
> Gerlando Falauto reported that when HRTICK is enabled, it is
> possible to trigger system deadlocks. These were hard to
> reproduce, as HRTICK has been broken in the past, but seemed
> to be connected to the timekeeping_seq lock.
> 
> Since seqlock/seqcount's aren't supported w/ lockdep, I added
> some extra spinlock based locking and triggered the following
> lockdep output:
> 
> [   15.849182] ntpd/4062 is trying to acquire lock:
> [   15.849765]  (&(&pool->lock)->rlock){..-...}, at: [<ffffffff810aa9b5>] __queue_work+0x145/0x480
> [   15.850051]
> [   15.850051] but task is already holding lock:
> [   15.850051]  (timekeeper_lock){-.-.-.}, at: [<ffffffff810df6df>] do_adjtimex+0x7f/0x100
> 
> <snip>
> 
> [   15.850051] Chain exists of: &(&pool->lock)->rlock --> &p->pi_lock --> timekeeper_lock
> [   15.850051]  Possible unsafe locking scenario:
> [   15.850051]
> [   15.850051]        CPU0                    CPU1
> [   15.850051]        ----                    ----
> [   15.850051]   lock(timekeeper_lock);
> [   15.850051]                                lock(&p->pi_lock);
> [   15.850051] lock(timekeeper_lock);
> [   15.850051] lock(&(&pool->lock)->rlock);
> [   15.850051]
> [   15.850051]  *** DEADLOCK ***
> 
> The deadlock was introduced by 06c017fdd4dc48451a ("timekeeping:
> Hold timekeepering locks in do_adjtimex and hardpps") in 3.10
> 
> This patch avoids this deadlock, by moving the call to
> schedule_delayed_work() outside of the timekeeper lock
> critical section.
> 
> Reported-by: Gerlando Falauto <gerlando.falauto@keymile.com>
> Tested-by: Lin Ming <minggr@gmail.com>
> Signed-off-by: John Stultz <john.stultz@linaro.org>
> Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
> Cc: stable <stable@vger.kernel.org> #3.11, 3.10
> Link: http://lkml.kernel.org/r/1378943457-27314-1-git-send-email-john.stultz@linaro.org
> Signed-off-by: Ingo Molnar <mingo@kernel.org>
> ---
>  include/linux/timex.h     | 1 +
>  kernel/time/ntp.c         | 6 ++----
>  kernel/time/timekeeping.c | 2 ++
>  3 files changed, 5 insertions(+), 4 deletions(-)
> 
> diff --git a/include/linux/timex.h b/include/linux/timex.h
> index b3726e6..dd3edd7 100644
> --- a/include/linux/timex.h
> +++ b/include/linux/timex.h
> @@ -141,6 +141,7 @@ extern int do_adjtimex(struct timex *);
>  extern void hardpps(const struct timespec *, const struct timespec *);
>  
>  int read_current_timer(unsigned long *timer_val);
> +void ntp_notify_cmos_timer(void);
>  
>  /* The clock frequency of the i8253/i8254 PIT */
>  #define PIT_TICK_RATE 1193182ul
> diff --git a/kernel/time/ntp.c b/kernel/time/ntp.c
> index 8f5b3b9..bb22151 100644
> --- a/kernel/time/ntp.c
> +++ b/kernel/time/ntp.c
> @@ -516,13 +516,13 @@ static void sync_cmos_clock(struct work_struct *work)
>  	schedule_delayed_work(&sync_cmos_work, timespec_to_jiffies(&next));
>  }
>  
> -static void notify_cmos_timer(void)
> +void ntp_notify_cmos_timer(void)
>  {
>  	schedule_delayed_work(&sync_cmos_work, 0);
>  }
>  
>  #else
> -static inline void notify_cmos_timer(void) { }
> +void ntp_notify_cmos_timer(void) { }
>  #endif
>  
>  
> @@ -687,8 +687,6 @@ int __do_adjtimex(struct timex *txc, struct timespec *ts, s32 *time_tai)
>  	if (!(time_status & STA_NANO))
>  		txc->time.tv_usec /= NSEC_PER_USEC;
>  
> -	notify_cmos_timer();
> -
>  	return result;
>  }
>  
> diff --git a/kernel/time/timekeeping.c b/kernel/time/timekeeping.c
> index 48b9fff..947ba25 100644
> --- a/kernel/time/timekeeping.c
> +++ b/kernel/time/timekeeping.c
> @@ -1703,6 +1703,8 @@ int do_adjtimex(struct timex *txc)
>  	write_seqcount_end(&timekeeper_seq);
>  	raw_spin_unlock_irqrestore(&timekeeper_lock, flags);
>  
> +	ntp_notify_cmos_timer();
> +
>  	return ret;
>  }
>  

-- 
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com

       reply	other threads:[~2013-09-16 16:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1378943457-27314-1-git-send-email-john.stultz@linaro.org>
     [not found] ` <tip-7bd36014460f793c19e7d6c94dab67b0afcfcb7f@git.kernel.org>
2013-09-16 16:04   ` Mathieu Desnoyers [this message]
2013-09-17  7:07     ` [tip:timers/urgent] timekeeping: Fix HRTICK related deadlock from ntp lock changes Ingo Molnar
2013-09-17  8:09       ` Mathieu Desnoyers
2013-09-17  8:26         ` Ingo Molnar
2013-09-17 16:33           ` Mathieu Desnoyers

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=20130916160426.GA24669@Krystal \
    --to=mathieu.desnoyers@efficios.com \
    --cc=gerlando.falauto@keymile.com \
    --cc=hpa@zytor.com \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=lttng-dev@lists.lttng.org \
    --cc=minggr@gmail.com \
    --cc=mingo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).