From: Liam Howlett <liam.howlett@oracle.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: open list <linux-kernel@vger.kernel.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Andrew Morton <akpm@linux-foundation.org>,
Matthew Wilcox <willy@infradead.org>,
David Howells <dhowells@redhat.com>,
Catalin Marinas <catalin.marinas@arm.com>,
SeongJae Park <sj@kernel.org>, Vlastimil Babka <vbabka@suse.cz>,
Will Deacon <will@kernel.org>,
Davidlohr Bueso <dave@stgolabs.net>
Subject: Re: BUG: kernel NULL pointer dereference, address: 00000004 - mas_update_gap
Date: Tue, 17 May 2022 15:27:08 +0000 [thread overview]
Message-ID: <20220517152702.rttuqbgx7f4idhd7@revolver> (raw)
In-Reply-To: <CA+G9fYuOHwkkqTdcqGa7kazBwCOF-P0Kw0gthvAzjU0t5EVSAQ@mail.gmail.com>
* Naresh Kamboju <naresh.kamboju@linaro.org> [220516 02:35]:
> While running LTP sched tests on i386 the following kernel BUG noticed on
> Linux next-20220513 [1].
>
...
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> metadata:
> git_ref: master
> git_repo: ''
> git_sha: 1e1b28b936aed946122b4e0991e7144fdbbfd77e
> git_describe: next-20220513
> kernel_version: 5.18.0-rc6
> kernel-config: https://builds.tuxbuild.com/296PiI1oM7N6Vk7m9lxuipmXW7B/config
> build-url: https://gitlab.com/Linaro/lkft/mirrors/next/linux-next/-/pipelines/538244935
> artifact-location: https://builds.tuxbuild.com/296PiI1oM7N6Vk7m9lxuipmXW7B
> toolchain: gcc-11
>
> --
> Linaro LKFT
> https://lkft.linaro.org
>
> [1] https://lkft.validation.linaro.org/scheduler/job/5021335#L1718
I was able to reproduce this issue with ltp running:
"./runltp -p -q -f sched"
I have sent a fix out [1] that allows the test to execute on i386 qemu.
Thanks,
Liam
1. https://lore.kernel.org/linux-mm/20220517152209.3486724-1-Liam.Howlett@oracle.com/
prev parent reply other threads:[~2022-05-17 15:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 6:34 Naresh Kamboju
2022-05-17 15:27 ` Liam Howlett [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=20220517152702.rttuqbgx7f4idhd7@revolver \
--to=liam.howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=dave@stgolabs.net \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=naresh.kamboju@linaro.org \
--cc=sfr@canb.auug.org.au \
--cc=sj@kernel.org \
--cc=vbabka@suse.cz \
--cc=will@kernel.org \
--cc=willy@infradead.org \
/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