From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org,
linux-rt-users <linux-rt-users@vger.kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Carsten Emde <C.Emde@osadl.org>, John Kacur <jkacur@redhat.com>,
<stable@vger.kernel.org>, <stable-rt@vger.kernel.org>
Subject: [PATCH RT 1/5] sched: Adjust sched_reset_on_fork when nothing else changes
Date: Fri, 21 Dec 2012 23:25:16 -0500 [thread overview]
Message-ID: <20121222042553.675639341@goodmis.org> (raw)
In-Reply-To: 20121222042515.867823077@goodmis.org
[-- Attachment #1: 0001-sched-Adjust-sched_reset_on_fork-when-nothing-else-c.patch --]
[-- Type: text/plain, Size: 859 bytes --]
From: Thomas Gleixner <tglx@linutronix.de>
If the policy and priority remain unchanged a possible modification of
sched_reset_on_fork gets lost in the early exit path.
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Cc: stable@vger.kernel.org
Cc: stable-rt@vger.kernel.org
---
kernel/sched/core.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index 1f9d6f5..3753bda 100644
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -4441,11 +4441,13 @@ recheck:
}
/*
- * If not changing anything there's no need to proceed further:
+ * If not changing anything there's no need to proceed
+ * further, but store a possible modification of
+ * reset_on_fork.
*/
if (unlikely(policy == p->policy && (!rt_policy(policy) ||
param->sched_priority == p->rt_priority))) {
next prev parent reply other threads:[~2012-12-22 4:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-22 4:25 [PATCH RT 0/5] [ANNOUNCE] 3.4.24-rt36-rc1 stable review Steven Rostedt
2012-12-22 4:25 ` Steven Rostedt [this message]
2012-12-22 4:25 ` [PATCH RT 2/5] sched: Queue RT tasks to head when prio drops Steven Rostedt
2012-12-22 4:25 ` [PATCH RT 3/5] sched: Consider pi boosting in setscheduler Steven Rostedt
2012-12-22 4:25 ` [PATCH RT 4/5] block: Use cpu_chill() for retry loops Steven Rostedt
2012-12-22 4:25 ` [PATCH RT 5/5] Linux 3.4.24-rt36-rc1 Steven Rostedt
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=20121222042553.675639341@goodmis.org \
--to=rostedt@goodmis.org \
--cc=C.Emde@osadl.org \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=stable-rt@vger.kernel.org \
--cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).