From: Andreas Schwab <schwab@linux-m68k.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: rppt@linux.ibm.com, Michael Schmitz <schmitzmic@gmail.com>,
Sam Creasey <sammy@sammy.net>, Greg Ungerer <gerg@linux-m68k.org>,
linux-m68k <linux-m68k@lists.linux-m68k.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] m68k: Fix memblock-related crashes
Date: Mon, 17 Dec 2018 20:00:16 +0100 [thread overview]
Message-ID: <87a7l4rnb3.fsf@igel.home> (raw)
In-Reply-To: <87o99pmib8.fsf@igel.home> (Andreas Schwab's message of "Thu, 13 Dec 2018 18:45:47 +0100")
On Dez 13 2018, Andreas Schwab <schwab@linux-m68k.org> wrote:
> I'm now getting this Oops:
>
> [ 65.390000] Unable to handle kernel NULL pointer dereference at virtual address (ptrval)
> [ 65.390000] Oops: 00000000
> [ 65.390000] Modules linked in: nls_iso8859_1 nls_cp437 vfat fat virtio_rng virtio_blk virtio_ring virtio xfs btrfs xor zlib_deflate raid6_pq libcrc32c reiserfs squashfs fuse dm_snapshot dm_bufio dm_mod binfmt_misc loop sg
> [ 65.390000] PC: [<00211544>] blk_throtl_bio+0x10e/0x592
And the crash does not occur when I revert commit 1008a11590.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2018-12-17 19:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 16:50 [PATCH v3] m68k: Fix memblock-related crashes Geert Uytterhoeven
2018-12-07 21:02 ` Mike Rapoport
2018-12-08 10:51 ` Geert Uytterhoeven
2018-12-08 11:17 ` John Paul Adrian Glaubitz
2018-12-08 17:11 ` Mike Rapoport
2018-12-12 14:58 ` Geert Uytterhoeven
2018-12-13 17:45 ` Andreas Schwab
2018-12-17 19:00 ` Andreas Schwab [this message]
2018-12-17 19:34 ` Andreas Schwab
2018-12-19 9:34 ` Geert Uytterhoeven
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=87a7l4rnb3.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=gerg@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=rppt@linux.ibm.com \
--cc=sammy@sammy.net \
--cc=schmitzmic@gmail.com \
/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