From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "fengguang.wu@intel.com" <fengguang.wu@intel.com>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Cc: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Bart Van Assche <Bart.VanAssche@wdc.com>,
"bp@alien8.de" <bp@alien8.de>,
"axboe@kernel.dk" <axboe@kernel.dk>
Subject: Re: [cdrom_check_status] BUG: unable to handle kernel NULL pointer dereference at 000001c0
Date: Tue, 7 Nov 2017 16:29:31 +0000 [thread overview]
Message-ID: <1510072170.2656.19.camel@wdc.com> (raw)
In-Reply-To: <20171107102538.mzbfdxll3fpf2kqg@wfg-t540p.sh.intel.com>
On Tue, 2017-11-07 at 18:25 +0800, Fengguang Wu wrote:
> [ 22.666764] BUG: unable to handle kernel NULL pointer dereference at 000001c0
> [ 22.666773] IP: cdrom_check_status+0x2c/0x90
If it is a regression then this patch might fix this kernel oops:
https://www.mail-archive.com/linux-block@vger.kernel.org/msg15155.html
Bart.
next prev parent reply other threads:[~2017-11-07 16:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20171108162818epcas2p25c73e1093a9d8f20d9efb2f3cd469b45@epcas2p2.samsung.com>
2017-11-07 10:25 ` [cdrom_check_status] BUG: unable to handle kernel NULL pointer dereference at 000001c0 Fengguang Wu
2017-11-07 10:43 ` Borislav Petkov
2017-11-07 13:06 ` Fengguang Wu
2017-11-07 14:01 ` Borislav Petkov
2017-11-07 16:01 ` Linus Torvalds
2017-11-07 16:37 ` [PATCH] drivers/ide-cd: Handle missing driver data during status check gracefully Borislav Petkov
2017-11-07 17:13 ` Linus Torvalds
2017-11-08 0:08 ` David Miller
2017-11-07 16:34 ` [cdrom_check_status] BUG: unable to handle kernel NULL pointer dereference at 000001c0 Fengguang Wu
2017-11-07 16:29 ` Bart Van Assche [this message]
2017-11-08 16:28 ` Bartlomiej Zolnierkiewicz
2017-11-08 16:50 ` Bartlomiej Zolnierkiewicz
2017-11-08 18:09 ` Bartlomiej Zolnierkiewicz
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=1510072170.2656.19.camel@wdc.com \
--to=bart.vanassche@wdc.com \
--cc=axboe@kernel.dk \
--cc=bp@alien8.de \
--cc=davem@davemloft.net \
--cc=fengguang.wu@intel.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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.