From: akpm@linux-foundation.org
To: mm-commits@vger.kernel.org
Cc: yong.zhang@windriver.com, mingo@elte.hu, oleg@redhat.com,
peterz@infradead.org, tglx@linutronix.de, yong.zhang0@gmail.com
Subject: + timer-make-try_to_del_timer_sync-safe-on-both-hardirq-context-and-up.patch added to -mm tree
Date: Fri, 24 Sep 2010 15:09:06 -0700 [thread overview]
Message-ID: <201009242209.o8OM96ds028177@imap1.linux-foundation.org> (raw)
The patch titled
timer: make try_to_del_timer_sync() safe on both hardirq context and UP
has been added to the -mm tree. Its filename is
timer-make-try_to_del_timer_sync-safe-on-both-hardirq-context-and-up.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find
out what to do about this
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: timer: make try_to_del_timer_sync() safe on both hardirq context and UP
From: Yong Zhang <yong.zhang@windriver.com>
In commit fd450b7318b75343f ("timers: introduce try_to_del_timer_sync()")
, it was saying try_to_del_timer_sync() can be used in interrupt context.
But because base->running_timer is SMP special, this lead to unsymmetry
try_to_del_timer_sync() on UP and SMP.
We can make running_timer live on everywhere, then try_to_del_timer_sync()
is also UP safe and can be used in hardirq context.
Signed-off-by: Yong Zhang <yong.zhang0@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Peter Zijlstra <peterz@infradead.org>
Acked-by: Oleg Nesterov <oleg@redhat.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
include/linux/timer.h | 4 ++--
kernel/timer.c | 6 +-----
2 files changed, 3 insertions(+), 7 deletions(-)
diff -puN include/linux/timer.h~timer-make-try_to_del_timer_sync-safe-on-both-hardirq-context-and-up include/linux/timer.h
--- a/include/linux/timer.h~timer-make-try_to_del_timer_sync-safe-on-both-hardirq-context-and-up
+++ a/include/linux/timer.h
@@ -249,11 +249,11 @@ static inline void timer_stats_timer_cle
extern void add_timer(struct timer_list *timer);
+extern int try_to_del_timer_sync(struct timer_list *timer);
+
#ifdef CONFIG_SMP
- extern int try_to_del_timer_sync(struct timer_list *timer);
extern int del_timer_sync(struct timer_list *timer);
#else
-# define try_to_del_timer_sync(t) del_timer(t)
# define del_timer_sync(t) del_timer(t)
#endif
diff -puN kernel/timer.c~timer-make-try_to_del_timer_sync-safe-on-both-hardirq-context-and-up kernel/timer.c
--- a/kernel/timer.c~timer-make-try_to_del_timer_sync-safe-on-both-hardirq-context-and-up
+++ a/kernel/timer.c
@@ -347,9 +347,7 @@ EXPORT_SYMBOL_GPL(set_timer_slack);
static inline void set_running_timer(struct tvec_base *base,
struct timer_list *timer)
{
-#ifdef CONFIG_SMP
base->running_timer = timer;
-#endif
}
static void internal_add_timer(struct tvec_base *base, struct timer_list *timer)
@@ -936,15 +934,12 @@ int del_timer(struct timer_list *timer)
}
EXPORT_SYMBOL(del_timer);
-#ifdef CONFIG_SMP
/**
* try_to_del_timer_sync - Try to deactivate a timer
* @timer: timer do del
*
* This function tries to deactivate a timer. Upon successful (ret >= 0)
* exit the timer is not queued and the handler is not running on any CPU.
- *
- * It must not be called from interrupt contexts.
*/
int try_to_del_timer_sync(struct timer_list *timer)
{
@@ -973,6 +968,7 @@ out:
}
EXPORT_SYMBOL(try_to_del_timer_sync);
+#ifdef CONFIG_SMP
/**
* del_timer_sync - deactivate a timer and wait for the handler to finish.
* @timer: the timer to be deactivated
_
Patches currently in -mm which might be from yong.zhang@windriver.com are
linux-next.patch
timer-make-try_to_del_timer_sync-safe-on-both-hardirq-context-and-up.patch
timer-del_timer_sync-can-be-used-in-softirq-context.patch
timer-warn-when-del_timer_sync-used-in-hardirq-context.patch
reply other threads:[~2010-09-24 22:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201009242209.o8OM96ds028177@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mm-commits@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=yong.zhang0@gmail.com \
--cc=yong.zhang@windriver.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