From: tip-bot for Ben Segall <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, bsegall@google.com, hpa@zytor.com,
mingo@kernel.org, peterz@infradead.org, tglx@linutronix.de
Subject: [tip:sched/core] sched: Fix cfs_bandwidth misuse of hrtimer_expires_remaining
Date: Tue, 29 Oct 2013 07:07:22 -0700 [thread overview]
Message-ID: <tip-db06e78cc13d70f10877e0557becc88ab3ad2be8@git.kernel.org> (raw)
In-Reply-To: <20131016181617.22647.73829.stgit@sword-of-the-dawn.mtv.corp.google.com>
Commit-ID: db06e78cc13d70f10877e0557becc88ab3ad2be8
Gitweb: http://git.kernel.org/tip/db06e78cc13d70f10877e0557becc88ab3ad2be8
Author: Ben Segall <bsegall@google.com>
AuthorDate: Wed, 16 Oct 2013 11:16:17 -0700
Committer: Ingo Molnar <mingo@kernel.org>
CommitDate: Tue, 29 Oct 2013 12:02:20 +0100
sched: Fix cfs_bandwidth misuse of hrtimer_expires_remaining
hrtimer_expires_remaining does not take internal hrtimer locks and thus
must be guarded against concurrent __hrtimer_start_range_ns (but
returning HRTIMER_RESTART is safe). Use cfs_b->lock to make it safe.
Signed-off-by: Ben Segall <bsegall@google.com>
Signed-off-by: Peter Zijlstra <peterz@infradead.org>
Cc: pjt@google.com
Link: http://lkml.kernel.org/r/20131016181617.22647.73829.stgit@sword-of-the-dawn.mtv.corp.google.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
kernel/sched/fair.c | 14 +++++++++++---
1 file changed, 11 insertions(+), 3 deletions(-)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index ebd187f..897d977 100644
--- a/kernel/sched/fair.c
+++ b/kernel/sched/fair.c
@@ -3285,7 +3285,13 @@ static const u64 min_bandwidth_expiration = 2 * NSEC_PER_MSEC;
/* how long we wait to gather additional slack before distributing */
static const u64 cfs_bandwidth_slack_period = 5 * NSEC_PER_MSEC;
-/* are we near the end of the current quota period? */
+/*
+ * Are we near the end of the current quota period?
+ *
+ * Requires cfs_b->lock for hrtimer_expires_remaining to be safe against the
+ * hrtimer base being cleared by __hrtimer_start_range_ns. In the case of
+ * migrate_hrtimers, base is never cleared, so we are fine.
+ */
static int runtime_refresh_within(struct cfs_bandwidth *cfs_b, u64 min_expire)
{
struct hrtimer *refresh_timer = &cfs_b->period_timer;
@@ -3361,10 +3367,12 @@ static void do_sched_cfs_slack_timer(struct cfs_bandwidth *cfs_b)
u64 expires;
/* confirm we're still not at a refresh boundary */
- if (runtime_refresh_within(cfs_b, min_bandwidth_expiration))
+ raw_spin_lock(&cfs_b->lock);
+ if (runtime_refresh_within(cfs_b, min_bandwidth_expiration)) {
+ raw_spin_unlock(&cfs_b->lock);
return;
+ }
- raw_spin_lock(&cfs_b->lock);
if (cfs_b->quota != RUNTIME_INF && cfs_b->runtime > slice) {
runtime = cfs_b->runtime;
cfs_b->runtime = 0;
next prev parent reply other threads:[~2013-10-29 14:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 18:16 [PATCH 0/5] Fix several races in CFS_BANDWIDTH Ben Segall
2013-10-16 18:16 ` [PATCH 1/5] sched: Fix race on toggling cfs_bandwidth_used Ben Segall
2013-10-29 14:07 ` [tip:sched/core] " tip-bot for Ben Segall
2013-10-16 18:16 ` [PATCH 2/5] sched: Fix cfs_bandwidth misuse of hrtimer_expires_remaining Ben Segall
2013-10-16 18:41 ` Peter Zijlstra
2013-10-16 19:12 ` bsegall
2013-10-29 14:07 ` tip-bot for Ben Segall [this message]
2013-10-16 18:16 ` [PATCH 3/5] sched: Fix hrtimer_cancel/rq->lock deadlock Ben Segall
2013-10-29 14:07 ` [tip:sched/core] sched: Fix hrtimer_cancel()/rq->lock deadlock tip-bot for Ben Segall
2013-10-16 18:16 ` [PATCH 4/5] sched: Guarantee new group-entities always have weight Ben Segall
2013-10-16 22:01 ` Peter Zijlstra
2013-10-16 22:16 ` Paul Turner
2013-10-16 22:22 ` Peter Zijlstra
2013-10-16 22:40 ` bsegall
2013-10-29 14:07 ` [tip:sched/core] " tip-bot for Paul Turner
2013-10-16 18:16 ` [PATCH 5/5] sched: Avoid throttle_cfs_rq racing with period_timer stopping Ben Segall
2013-10-16 22:06 ` Peter Zijlstra
2013-10-29 14:07 ` [tip:sched/core] sched: Avoid throttle_cfs_rq() " tip-bot for Ben Segall
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=tip-db06e78cc13d70f10877e0557becc88ab3ad2be8@git.kernel.org \
--to=tipbot@zytor.com \
--cc=bsegall@google.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--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