From: Peter Zijlstra <peterz@infradead.org>
To: Yi Wang <wang.yi59@zte.com.cn>
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org,
jiang.biao2@zte.com.cn, zhong.weidong@zte.com.cn
Subject: Re: [PATCH] sched/topology: check variable group before dereferenced
Date: Mon, 23 Jul 2018 10:37:02 +0200 [thread overview]
Message-ID: <20180723083702.GW2494@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <1532319547-33335-1-git-send-email-wang.yi59@zte.com.cn>
On Mon, Jul 23, 2018 at 12:19:07PM +0800, Yi Wang wrote:
> The variable group in sched_domain_debug_one() is not checked
> when firstly used in cpumask_test_cpu(cpu, sched_group_span(group)),
> but it maybe NULL(checked later in the following while loop) and may
> cause NULL pointer dereference without checking. We need to check it
> before using to avoid NULL dereference.
It being NULL really is a fairly severe error in construction; but sure.
This patch won't hurt.
> Signed-off-by: Yi Wang <wang.yi59@zte.com.cn>
> Reviewed-by: Jiang Biao <jiang.biao2@zte.com.cn>
> ---
> kernel/sched/topology.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/sched/topology.c b/kernel/sched/topology.c
> index 5ac724b..c7cf87c 100644
> --- a/kernel/sched/topology.c
> +++ b/kernel/sched/topology.c
> @@ -53,7 +53,7 @@ static int sched_domain_debug_one(struct sched_domain *sd, int cpu, int level,
> printk(KERN_ERR "ERROR: domain->span does not contain "
> "CPU%d\n", cpu);
> }
> - if (!cpumask_test_cpu(cpu, sched_group_span(group))) {
> + if (group && !cpumask_test_cpu(cpu, sched_group_span(group))) {
> printk(KERN_ERR "ERROR: domain->groups does not contain"
> " CPU%d\n", cpu);
> }
> --
> 1.8.3.1
>
next prev parent reply other threads:[~2018-07-23 8:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-23 4:19 Yi Wang
2018-07-23 8:37 ` Peter Zijlstra [this message]
2018-07-25 14:20 ` [tip:sched/core] sched/topology: Check variable group before dereferencing it tip-bot for Yi Wang
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=20180723083702.GW2494@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=jiang.biao2@zte.com.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=wang.yi59@zte.com.cn \
--cc=zhong.weidong@zte.com.cn \
/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
all inboxes | Powered by JetHome®