From: Mark Brown <broonie@kernel.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
open list <linux-kernel@vger.kernel.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
lkft-triage@lists.linaro.org, regressions@lists.linux.dev,
Kefeng Wang <wangkefeng.wang@huawei.com>,
Andrew Morton <akpm@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>,
Anders Roxell <anders.roxell@linaro.org>
Subject: Re: next: BUG: kernel NULL pointer dereference, address: 0000000000000008 - RIP: 0010:do_wp_page
Date: Fri, 13 Jan 2023 17:29:16 +0000 [thread overview]
Message-ID: <Y8GU7Pqq/z0wxwgs@sirena.org.uk> (raw)
In-Reply-To: <Y8F+iKuJWAFsUg2m@casper.infradead.org>
[-- Attachment #1: Type: text/plain, Size: 1041 bytes --]
On Fri, Jan 13, 2023 at 03:53:44PM +0000, Matthew Wilcox wrote:
> On Fri, Jan 13, 2023 at 09:14:15PM +0530, Naresh Kamboju wrote:
> > [ 15.980869] Hardware name: Supermicro SYS-5019S-ML/X11SSH-F, BIOS
> > 2.0b 07/27/2017
> > [ 15.988336] RIP: 0010:do_wp_page (memory.c:?)
> Uh, are you compiling your kernels without debuginfo? The results
> from syzbot & 0day are much more useful:
> https://lore.kernel.org/linux-mm/Y8FnAwWOxLrfoWTN@casper.infradead.org/T/#u
> for an example.
This will be a consequence of x86 not including DEBUG_INFO in defconfig
- a lot of the testing systems cover unmodified upstream configs as a
baseline, it tends to make life easier and be an indication of what
people want covering. A quick survey says most architectures are
setting at least DEBUG_INFO_REDUCED, it'd probably be a good idea for
x86 to do so as well. The logs from arm64 and probably also arm
(depending on exactly which config was being covered) should be more
usefully decodable, Naresh you mentioned that those were also failing?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 484 bytes --]
next prev parent reply other threads:[~2023-01-13 17:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 13:23 next: BUG: kernel NULL pointer dereference, address: 0000000000000008 - RIP: 0010:do_wp_page Naresh Kamboju
2023-01-13 14:02 ` Matthew Wilcox
2023-01-13 15:44 ` Naresh Kamboju
2023-01-13 15:53 ` Matthew Wilcox
2023-01-13 16:41 ` Naresh Kamboju
2023-01-13 17:29 ` Mark Brown [this message]
2023-01-13 19:43 ` Mark Brown
2023-01-13 19:54 ` Matthew Wilcox
2023-01-13 20:30 ` Mark Brown
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=Y8GU7Pqq/z0wxwgs@sirena.org.uk \
--to=broonie@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=regressions@lists.linux.dev \
--cc=wangkefeng.wang@huawei.com \
--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