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 20:30:26 +0000 [thread overview]
Message-ID: <Y8G/Yu22ZfUoQbed@sirena.org.uk> (raw)
In-Reply-To: <Y8G27N+0Mpr9WmgD@casper.infradead.org>
[-- Attachment #1: Type: text/plain, Size: 547 bytes --]
On Fri, Jan 13, 2023 at 07:54:20PM +0000, Matthew Wilcox wrote:
> On Fri, Jan 13, 2023 at 07:43:58PM +0000, Mark Brown wrote:
> > On Fri, Jan 13, 2023 at 03:53:44PM +0000, Matthew Wilcox wrote:
> > > Uh, are you compiling your kernels without debuginfo? The results
> > > from syzbot & 0day are much more useful:
> > FWIW here's a decode from arm64 (the boards I sampled all looked very
> > similar):
> We've identified the bad commit now ... this thread is just about
> improving the process for next time ;-)
Ah, OK - I missed that thread.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2023-01-13 20:30 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
2023-01-13 19:43 ` Mark Brown
2023-01-13 19:54 ` Matthew Wilcox
2023-01-13 20:30 ` Mark Brown [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=Y8G/Yu22ZfUoQbed@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