[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191107194232.GA58063@google.com>
Date: Thu, 7 Nov 2019 19:42:32 +0000
From: Quentin Perret <qperret@...gle.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Kirill Tkhai <ktkhai@...tuozzo.com>, linux-kernel@...r.kernel.org,
aaron.lwe@...il.com, valentin.schneider@....com, mingo@...nel.org,
pauld@...hat.com, jdesfossez@...italocean.com,
naravamudan@...italocean.com, vincent.guittot@...aro.org,
dietmar.eggemann@....com, juri.lelli@...hat.com,
rostedt@...dmis.org, bsegall@...gle.com, mgorman@...e.de,
kernel-team@...roid.com, john.stultz@...aro.org
Subject: Re: NULL pointer dereference in pick_next_task_fair
On Thursday 07 Nov 2019 at 20:31:34 (+0100), Peter Zijlstra wrote:
> Thing is, if we revert (and we might have to), we'll have to revert more
> than just the one patch due to that other (__pick_migrate_task) borkage
> that got reported today.
Fair enough, let's try an avoid reverting the world if possible ...
I'll give a go to your patch tomorrow first thing.
Cheers,
Quentin
Powered by blists - more mailing lists