From: Yong Zhang <yong.zhang0@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: tglx@linutronix.de, akpm@linux-foundation.org, mingo@elte.hu,
oleg@redhat.com, peterz@infradead.org
Subject: [RFC V2 PATCH 0/3] timer: patchset focus on del_timer_sync()
Date: Wed, 25 Aug 2010 21:45:56 +0800 [thread overview]
Message-ID: <1282743959-5427-1-git-send-email-yong.zhang0@gmail.com> (raw)
From: Yong Zhang <yong.zhang@windriver.com>
This is inspired by http://lkml.org/lkml/2010/8/16/291
which catch a lockdep false positive on fake_timer_lock.
When I go into del_timer_sync(), but don't find anything
which prevent del_timer_sync() from using in softirq context,
and indeed it's been used in softirq for some timer(such as
__dst_free()).
Thus, tell others it can't be used in softirq context, and
teach lockdep about that. It's realized by patch-0002.
Your comments are very appreciated.
Thanks,
Yong
V2 <- V1
Update patch 0001, the new version make try_to_del_timer_sync()
safe on both hardirq context and UP. Thanks Oleg.
---
Yong Zhang (3):
timer: make try_to_del_timer_sync() safe on both hardirq context and UP
timer: del_timer_sync() can be used in softirq context
timer: warn when del_timer_sync() used in hardirq context
include/linux/timer.h | 4 ++--
kernel/timer.c | 20 +++++++++-----------
2 files changed, 11 insertions(+), 13 deletions(-)
next reply other threads:[~2010-08-25 13:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 13:45 Yong Zhang [this message]
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
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=1282743959-5427-1-git-send-email-yong.zhang0@gmail.com \
--to=yong.zhang0@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@redhat.com \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®