All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yong Zhang <yong.zhang0@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: tglx@linutronix.de, akpm@linux-foundation.org, mingo@elte.hu,
	peterz@infradead.org, oleg@redhat.com
Subject: [RFC PATCH 0/3] timer: patchset focus on del_timer_sync()
Date: Tue, 24 Aug 2010 14:58:46 +0800	[thread overview]
Message-ID: <1282633129-9187-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

---
Yong Zhang (3):
      timer: fix comments of try_to_del_timer_sync()
      timer: del_timer_sync() can be used in softirq context
      timer: warn when del_timer_sync() used in hardirq context

 kernel/timer.c |   16 ++++++++--------
 1 files changed, 8 insertions(+), 8 deletions(-)


             reply	other threads:[~2010-08-24  7:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-24  6:58 Yong Zhang [this message]
2010-08-24  6:58 ` [RFC PATCH 1/3] timer: fix comments of try_to_del_timer_sync() Yong Zhang
2010-08-24 12:11   ` Oleg Nesterov
2010-08-24 12:49     ` Yong Zhang
2010-08-24 16:31       ` Oleg Nesterov
2010-08-25  1:56         ` Yong Zhang
2010-08-24  6:58 ` [RFC PATCH 2/3] timer: del_timer_sync() can be used in softirq context Yong Zhang
2010-08-24  6:58 ` [RFC PATCH 3/3] timer: warn when del_timer_sync() used in hardirq context Yong Zhang

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=1282633129-9187-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 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.