mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Daniel Axtens <dja@axtens.net>
Cc: linux-kernel@vger.kernel.org, peterz@infradead.org,
	mingo@redhat.com,
	Konstantin Khlebnikov <khlebnikov@yandex-team.ru>,
	Ben Segall <bsegall@google.com>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: [PATCH] sched/debug: Fix SCHED_WARN_ON() to return a value on !CONFIG_SCHED_DEBUG as well
Date: Tue, 20 Jun 2017 12:27:42 +0200	[thread overview]
Message-ID: <20170620102742.p3qta5lrefhbyeen@gmail.com> (raw)
In-Reply-To: <20170510201139.16236-1-dja@axtens.net>


* Daniel Axtens <dja@axtens.net> wrote:

> If we set a next or last buddy for a se that is not on_rq, we will
> end up taking a NULL pointer dereference in wakeup_preempt_entity
> via pick_next_task_fair.
> 
> Detect when we would be about to do that, throw a warning and
> then refuse to actually set it.
> 
> This has been suggested at least twice[0][1]: just do it.
> 
> [0] https://marc.info/?l=linux-kernel&m=146651668921468&w=2
> [1] https://lkml.org/lkml/2016/6/16/663
> 
> Cc: Konstantin Khlebnikov <khlebnikov@yandex-team.ru>
> Cc: Ben Segall <bsegall@google.com>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Signed-off-by: Daniel Axtens <dja@axtens.net>
> 
> ---
> 
> I recently had to debug a problem with these (we hadn't backported
> Konstantin's patches in this area) and this would have saved a lot
> of time/pain.
> 
> v2: use SCHED_WARN_ON to restrict when the test is run. This is a
>     macro for WARN_ON_ONCE, which is convenient.
> ---
>  kernel/sched/fair.c | 10 ++++++++--
>  1 file changed, 8 insertions(+), 2 deletions(-)
> 
> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> index d71109321841..44b94cfe02cb 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -6168,8 +6168,11 @@ static void set_last_buddy(struct sched_entity *se)
>  	if (entity_is_task(se) && unlikely(task_of(se)->policy == SCHED_IDLE))
>  		return;
>  
> -	for_each_sched_entity(se)
> +	for_each_sched_entity(se) {
> +		if (SCHED_WARN_ON(!se->on_rq))
> +			return;
>  		cfs_rq_of(se)->last = se;
> +	}

This won't build in the !CONFIG_SCHED_DEBUG case, because of the naive definition 
in sched.h:

#define SCHED_WARN_ON(x)        ((void)(x))

That should be changed to something like:

#define SCHED_WARN_ON(x)        ((void)(x))

I've applied the fix below. (untested at the moment)

Thanks,

	Ingo

========================>
>From 6d3aed3d8a0573d0a6eb1160ccd0a0713f4dbc2f Mon Sep 17 00:00:00 2001
From: Ingo Molnar <mingo@kernel.org>
Date: Tue, 20 Jun 2017 12:24:42 +0200
Subject: [PATCH] sched/debug: Fix SCHED_WARN_ON() to return a value on !CONFIG_SCHED_DEBUG as well

This definition of SCHED_WARN_ON():

 #define SCHED_WARN_ON(x)        ((void)(x))

is not fully compatible with the 'real' WARN_ON_ONCE() primitive, as it
has no return value, so it cannot be used in conditionals.

Fix it.

Cc: Daniel Axtens <dja@axtens.net>
Cc: Konstantin Khlebnikov <khlebnikov@yandex-team.ru>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
 kernel/sched/sched.h | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/kernel/sched/sched.h b/kernel/sched/sched.h
index f2ef759a4cb6..e0329d10bdb8 100644
--- a/kernel/sched/sched.h
+++ b/kernel/sched/sched.h
@@ -39,9 +39,9 @@
 #include "cpuacct.h"
 
 #ifdef CONFIG_SCHED_DEBUG
-#define SCHED_WARN_ON(x)	WARN_ONCE(x, #x)
+# define SCHED_WARN_ON(x)	WARN_ONCE(x, #x)
 #else
-#define SCHED_WARN_ON(x)	((void)(x))
+# define SCHED_WARN_ON(x)	({ (void)(x), 0; })
 #endif
 
 struct rq;

  parent reply	other threads:[~2017-06-20 10:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-10 20:11 [PATCH v2] sched/fair: WARN and refuse to set buddy when !se->on_rq Daniel Axtens
2017-06-19 14:05 ` Daniel Axtens
2017-06-20  7:41   ` Konstantin Khlebnikov
2017-06-20 10:27 ` Ingo Molnar [this message]
2017-06-20 13:52   ` [PATCH] sched/debug: Fix SCHED_WARN_ON() to return a value on !CONFIG_SCHED_DEBUG as well Daniel Axtens
2017-06-20 13:26 ` [tip:sched/core] sched/fair: WARN() and refuse to set buddy when !se->on_rq tip-bot for Daniel Axtens

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=20170620102742.p3qta5lrefhbyeen@gmail.com \
    --to=mingo@kernel.org \
    --cc=bsegall@google.com \
    --cc=dja@axtens.net \
    --cc=khlebnikov@yandex-team.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@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

Powered by JetHome