From: Michael Ellerman <mpe@ellerman.id.au>
To: Matthew Wilcox <willy@infradead.org>
Cc: Zorro Lang <zlang@kernel.org>,
linux-mm@kvack.org, linux-ext4@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [Bug report] BUG: Kernel NULL pointer dereference at 0x00000069, filemap_release_folio+0x88/0xb0
Date: Wed, 05 Oct 2022 22:13:35 +1100 [thread overview]
Message-ID: <87bkqqplpc.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <Yzc8hJL6cqxXCKaJ@casper.infradead.org>
Matthew Wilcox <willy@infradead.org> writes:
> On Fri, Sep 30, 2022 at 12:01:26PM +1000, Michael Ellerman wrote:
>> Matthew Wilcox <willy@infradead.org> writes:
>> >> [ 4681.238745] Instruction dump:
>> >> [ 4681.238749] fbc1fff0 f821ffc1 7c7d1b78 7c9c2378 ebc30028 7fdff378 48000018 60000000
>> >> [ 4681.238765] 60000000 ebff0008 7c3ef840 41820048 <815f0060> e93f0000 5529077c 7d295378
>> >
>> > Running that through scripts/decodecode (with some minor hacks .. how
>> > do PPC people do this properly?)
>>
>> We've just always used our own scripts. Mine is here: https://github.com/mpe/misc-scripts/blob/master/ppc/ppc-disasm
>>
>> I've added an issue to our tracker for us to get scripts/decodecode
>> working on our oopses (eventually).
>
> Would you be open to changing your oops printer to do
> s/Instruction dump/Code/ ? That would make it work without any other
> changes.
Yeah, we're the only arch that uses "Instruction dump".
For userspace instructions we already print "code".
I'll send a patch switching to "Code:".
cheers
WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <mpe@ellerman.id.au>
To: Matthew Wilcox <willy@infradead.org>
Cc: linux-mm@kvack.org, linux-ext4@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, Zorro Lang <zlang@kernel.org>
Subject: Re: [Bug report] BUG: Kernel NULL pointer dereference at 0x00000069, filemap_release_folio+0x88/0xb0
Date: Wed, 05 Oct 2022 22:13:35 +1100 [thread overview]
Message-ID: <87bkqqplpc.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <Yzc8hJL6cqxXCKaJ@casper.infradead.org>
Matthew Wilcox <willy@infradead.org> writes:
> On Fri, Sep 30, 2022 at 12:01:26PM +1000, Michael Ellerman wrote:
>> Matthew Wilcox <willy@infradead.org> writes:
>> >> [ 4681.238745] Instruction dump:
>> >> [ 4681.238749] fbc1fff0 f821ffc1 7c7d1b78 7c9c2378 ebc30028 7fdff378 48000018 60000000
>> >> [ 4681.238765] 60000000 ebff0008 7c3ef840 41820048 <815f0060> e93f0000 5529077c 7d295378
>> >
>> > Running that through scripts/decodecode (with some minor hacks .. how
>> > do PPC people do this properly?)
>>
>> We've just always used our own scripts. Mine is here: https://github.com/mpe/misc-scripts/blob/master/ppc/ppc-disasm
>>
>> I've added an issue to our tracker for us to get scripts/decodecode
>> working on our oopses (eventually).
>
> Would you be open to changing your oops printer to do
> s/Instruction dump/Code/ ? That would make it work without any other
> changes.
Yeah, we're the only arch that uses "Instruction dump".
For userspace instructions we already print "code".
I'll send a patch switching to "Code:".
cheers
next prev parent reply other threads:[~2022-10-05 11:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 1:17 [Bug report] BUG: Kernel NULL pointer dereference at 0x00000069, filemap_release_folio+0x88/0xb0 Zorro Lang
2022-09-27 1:17 ` Zorro Lang
2022-09-29 21:28 ` Matthew Wilcox
2022-09-29 21:28 ` Matthew Wilcox
2022-09-30 2:01 ` Michael Ellerman
2022-09-30 18:59 ` Matthew Wilcox
2022-09-30 18:59 ` Matthew Wilcox
2022-10-05 11:13 ` Michael Ellerman [this message]
2022-10-05 11:13 ` Michael Ellerman
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=87bkqqplpc.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=willy@infradead.org \
--cc=zlang@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.