From: ebiederm@xmission.com (Eric W. Biederman)
To: kernel test robot <oliver.sang@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>, lkp@lists.01.org, lkp@intel.com
Subject: Re: [kthread] 40966e316f: WARNING:at_kernel/sched/core.c:#sched_init
Date: Fri, 17 Dec 2021 11:01:41 -0600 [thread overview]
Message-ID: <878rwjf9my.fsf@email.froward.int.ebiederm.org> (raw)
In-Reply-To: <20211216102956.GC10708@xsang-OptiPlex-9020> (kernel test robot's message of "Thu, 16 Dec 2021 18:29:56 +0800")
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
next prev parent reply other threads:[~2021-12-17 17:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 10:29 [kthread] 40966e316f: WARNING:at_kernel/sched/core.c:#sched_init kernel test robot
2021-12-17 17:01 ` Eric W. Biederman [this message]
2021-12-23 2:48 ` Oliver Sang
2021-12-23 3:31 ` Eric W. Biederman
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=878rwjf9my.fsf@email.froward.int.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=oliver.sang@intel.com \
/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