linux-kernel - Re: next: BUG: kernel NULL pointer dereference, address: 0000000000000008

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 13 Jan 2023 17:29:16 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Matthew Wilcox <willy@...radead.org>
Cc:     Naresh Kamboju <naresh.kamboju@...aro.org>,
        open list <linux-kernel@...r.kernel.org>,
        Linux-Next Mailing List <linux-next@...r.kernel.org>,
        lkft-triage@...ts.linaro.org, regressions@...ts.linux.dev,
        Kefeng Wang <wangkefeng.wang@...wei.com>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Arnd Bergmann <arnd@...db.de>,
        Anders Roxell <anders.roxell@...aro.org>
Subject: Re: next: BUG: kernel NULL pointer dereference, address:
 0000000000000008 - RIP: 0010:do_wp_page

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?

Download attachment "signature.asc" of type "application/pgp-signature" (485 bytes)