Messages in this thread | | | From | (Eric W. Biederman) | Date | Fri, 17 Dec 2021 11:01:41 -0600 | Subject | Re: [kthread] 40966e316f: WARNING:at_kernel/sched/core.c:#sched_init |
| |
kernel test robot <oliver.sang@intel.com> writes:
> Greeting, > > FYI, we noticed the following commit (built with gcc-9): > > commit: 40966e316f86b8cfd83abd31ccb4df729309d3e7 ("kthread: Ensure struct kthread is present for all kthreads") > https://git.kernel.org/cgit/linux/kernel/git/ebiederm/user-namespace.git signal-for-v5.17 > > in testcase: trinity > version: trinity-x86_64-608712d8-1_20211207 > with following parameters: > > runtime: 300s > > test-description: Trinity is a linux system call fuzz tester. > test-url: http://codemonkey.org.uk/projects/trinity/ > > > on test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G > > caused below changes (please refer to attached dmesg/kmsg for entire > log/backtrace):
Ok. That is very weird. I will dig into it.
Silly question is there anything in this testing to cause memory allocations to fail early in boot?
Eric
| |