[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210515210238.GG5618@worktop.programming.kicks-ass.net>
Date: Sat, 15 May 2021 23:02:38 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Khaled ROMDHANI <khaledromdhani216@...il.com>
Cc: mingo@...hat.com, juri.lelli@...hat.com,
vincent.guittot@...aro.org, dietmar.eggemann@....com,
rostedt@...dmis.org, bsegall@...gle.com, mgorman@...e.de,
bristot@...hat.com, linux-kernel@...r.kernel.org,
kernel-janitors@...r.kernel.org
Subject: Re: [PATCH-next] sched: Fix Null pointer derefrence
On Sat, May 15, 2021 at 05:46:45PM +0100, Khaled ROMDHANI wrote:
> The 'curr' variable could be NULL and derefrenced by
> pick_next_entity. Fix this by adding a check that prevent
> the invocation of pick_next_entity with a NULL passed argument.
And why exactly is that a problem?
Powered by blists - more mailing lists