From: Tejun Heo <tj@kernel.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Chris Worley <chris.worley@primarydata.com>,
linux-kernel@vger.kernel.org, bfields@fieldses.org,
Michael Skralivetsky <michael.skralivetsky@primarydata.com>,
Trond Myklebust <trond.myklebust@primarydata.com>,
Shaohua Li <shli@fb.com>, Jeff Layton <jlayton@poochiereds.net>,
kernel-team@fb.com
Subject: Re: [PATCH] timer: add_timer_on() should perform proper migration
Date: Wed, 4 Nov 2015 14:43:46 -0500 [thread overview]
Message-ID: <20151104194346.GA32152@mtj.duckdns.org> (raw)
In-Reply-To: <alpine.DEB.2.11.1511042025160.4032@nanos>
Hello, Thomas.
On Wed, Nov 04, 2015 at 08:35:00PM +0100, Thomas Gleixner wrote:
> nice detective work. This has been there forever. I really wonder why
> nobody ever triggered this before.
I guess there weren't enough concurrent del/add_timer_on() combos.
Workqueue recently switched to always use add_timer_on() from its
timer function making that a lot more frequent for heavy
mod_delayed_work_on() users and that's when it started surfacing.
Thanks.
--
tejun
prev parent reply other threads:[~2015-11-04 19:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 14:31 timer code oops when calling mod_delayed_work Jeff Layton
2015-10-29 17:58 ` Jeff Layton
2015-10-31 2:00 ` Tejun Heo
2015-10-31 11:34 ` Jeff Layton
2015-10-31 21:31 ` Tejun Heo
2015-10-31 21:54 ` Jeff Layton
2015-11-02 19:48 ` Chris Worley
2015-11-02 19:56 ` Jeff Layton
2015-11-03 1:33 ` Jeff Layton
2015-11-03 17:55 ` Jeff Layton
2015-11-03 22:54 ` Tejun Heo
2015-11-04 0:06 ` Tejun Heo
2015-11-04 11:48 ` Jeff Layton
2015-11-04 17:15 ` [PATCH] timer: add_timer_on() should perform proper migration Tejun Heo
2015-11-04 19:27 ` [tip:timers/urgent] timers: Use proper base migration in add_timer_on() tip-bot for Tejun Heo
2015-11-04 19:35 ` [PATCH] timer: add_timer_on() should perform proper migration Thomas Gleixner
2015-11-04 19:43 ` Tejun Heo [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=20151104194346.GA32152@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=bfields@fieldses.org \
--cc=chris.worley@primarydata.com \
--cc=jlayton@poochiereds.net \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.skralivetsky@primarydata.com \
--cc=shli@fb.com \
--cc=tglx@linutronix.de \
--cc=trond.myklebust@primarydata.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 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.