From: Oleg Nesterov <oleg@redhat.com>
To: Yong Zhang <yong.zhang0@gmail.com>
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de,
akpm@linux-foundation.org, mingo@elte.hu, peterz@infradead.org
Subject: Re: [RFC V2 PATCH 3/3] timer: warn when del_timer_sync() used in hardirq context
Date: Wed, 25 Aug 2010 20:22:04 +0200 [thread overview]
Message-ID: <20100825182204.GB22671@redhat.com> (raw)
In-Reply-To: <1282743959-5427-4-git-send-email-yong.zhang0@gmail.com>
On 08/25, Yong Zhang wrote:
>
> From: Yong Zhang <yong.zhang@windriver.com>
>
> Add explict warning to prevent del_timer_sync() from using
> in hardirq context.
Agreed, del_timer_sync() from softirq should be OK.
> Signed-off-by: Yong Zhang <yong.zhang0@gmail.com>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: Ingo Molnar <mingo@elte.hu>
> ---
> kernel/timer.c | 6 +++++-
> 1 files changed, 5 insertions(+), 1 deletions(-)
>
> diff --git a/kernel/timer.c b/kernel/timer.c
> index 08c9559..1bc4b4a 100644
> --- a/kernel/timer.c
> +++ b/kernel/timer.c
> @@ -996,7 +996,11 @@ int del_timer_sync(struct timer_list *timer)
> lock_map_release(&timer->lockdep_map);
> local_bh_enable();
> #endif
> -
> + /*
> + * don't use it in hardirq context, because it
> + * could lead to deadlock.
> + */
> + WARN_ON(in_irq());
> for (;;) {
> int ret = try_to_del_timer_sync(timer);
> if (ret >= 0)
> --
> 1.7.0.4
>
prev parent reply other threads:[~2010-08-25 18:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 13:45 [RFC V2 PATCH 0/3] timer: patchset focus on del_timer_sync() Yong Zhang
2010-08-25 13:45 ` [RFC V2 PATCH 1/3] timer: make try_to_del_timer_sync() safe on both hardirq context and UP Yong Zhang
2010-08-25 18:10 ` Oleg Nesterov
2010-08-25 13:45 ` [RFC V2 PATCH 2/3] timer: del_timer_sync() can be used in softirq context Yong Zhang
2010-08-25 13:45 ` [RFC V2 PATCH 3/3] timer: warn when del_timer_sync() used in hardirq context Yong Zhang
2010-08-25 18:22 ` Oleg Nesterov [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=20100825182204.GB22671@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=yong.zhang0@gmail.com \
/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