From: ebiederm@xmission.com (Eric W. Biederman)
To: Oliver Sang <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: Wed, 22 Dec 2021 21:31:22 -0600 [thread overview]
Message-ID: <87sfukuhdh.fsf@email.froward.int.ebiederm.org> (raw)
In-Reply-To: <20211223024800.GA33629@xsang-OptiPlex-9020> (Oliver Sang's message of "Thu, 23 Dec 2021 10:48:00 +0800")
Oliver Sang <oliver.sang@intel.com> writes:
> hi Eric,
>
> On Fri, Dec 17, 2021 at 11:01:41AM -0600, Eric W. Biederman wrote:
>> 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?
>
> we didn't observe it. actually test could finish for both this
> commit (though with reported warning) and parent. the only diff seems
> the reported warning.
>
> cead18552660702a 40966e316f86b8cfd83abd31ccb
> ---------------- ---------------------------
> fail:runs %reproduction fail:runs
> | | |
> :8 100% 8:8 dmesg.RIP:sched_init
> :8 100% 8:8 dmesg.WARNING:at_kernel/sched/core.c:#sched_init
>
> but could you check in dmesg we attached in original report for any suspicous
> memory issue?
>
> or could you help check the config we used (also attached in original report)
> to see if we can make some changes then to expose the possible memory issue,
> in case our current config cannot capture? Thanks
This was my bad. I have pushed the fix out now. I had the test
backwards in the WARN_ON.
My apologies for the noise.
Eric
prev parent reply other threads:[~2021-12-23 3:34 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
2021-12-23 2:48 ` Oliver Sang
2021-12-23 3:31 ` Eric W. Biederman [this message]
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=87sfukuhdh.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