[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a253ee7d-8351-4cd1-bebe-fca1370b4093@bytedance.com>
Date: Wed, 31 Jan 2024 20:34:09 +0800
From: Abel Wu <wuyun.abel@...edance.com>
To: Oliver Sang <oliver.sang@...el.com>
Cc: oe-lkp@...ts.linux.dev, lkp@...el.com, linux-kernel@...r.kernel.org,
Peter Zijlstra <peterz@...radead.org>, aubrey.li@...ux.intel.com,
yu.c.chen@...el.com, Tiwei Bie <tiwei.btw@...group.com>
Subject: Re: Re: [linus:master] [sched/eevdf] 2227a957e1:
BUG:kernel_NULL_pointer_dereference,address
On 1/30/24 10:09 PM, Oliver Sang Wrote:
> hi, Abel,
>
> On Tue, Jan 30, 2024 at 06:13:32PM +0800, Abel Wu wrote:
>> On 1/30/24 3:24 PM, kernel test robot Wrote:
>>>
>>> we found this issue happens in very random way (23 out of 999 runs).
>>> but keeps clean on parent.
>>
>> Thanks for reporting, I will try to reproduce the issue. Does the 'parent'
>> mean the same code branch without this commit?
>
>
> it just means the parent in git log.
>
> xsang@inn:/c/repo/linux$ git log --oneline --graph 2227a957e1
> * 2227a957e1d5b sched/eevdf: Sort the rbtree by virtual deadline
> * 84db47ca7146d sched/numa: Fix mm numa_scan_seq based unconditional scan <-- parent
Thanks for clarifying, Oliver. And can you please check the parent's
dmesg for the log:
pr_err("EEVDF scheduling fail, picking leftmost\n");
which potentially turns a kernel panic to a message.
Powered by blists - more mailing lists