From: Coly Li <i@coly.li>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>,
linux-bcache@vger.kernel.org
Cc: Michael Lyle <mlyle@lyle.org>
Subject: Re: bcache: for-next unable to handle kernel NULL pointer dereference at 0000000000000019
Date: Mon, 23 Oct 2017 21:05:24 +0800 [thread overview]
Message-ID: <08c770ef-eb09-ed55-a7bb-31b1b97a88d9@coly.li> (raw)
In-Reply-To: <b3fe481a-67d7-1e70-1f52-0aa285dc48e7@profihost.ag>
On 2017/10/23 下午8:59, Stefan Priebe - Profihost AG wrote:
> Hi Coly,
>
>
> Am 23.10.2017 um 14:56 schrieb Coly Li:
>> On 2017/10/23 下午7:42, Stefan Priebe - Profihost AG wrote:
>>> Hello,
>>>
>>> i picked all bcache patches from for-next to my 4.4 kernel to test the
>>> new controller.
>>>
>>> After doing so i see random kernel panics with the following trace:
>>
>> Hi Stefan,
>>
>> Thanks for the report. This is the 3rd report I see recently for NULL
>> pointer dereference, maybe they are related (or maybe not). Is it a
>> panic when bcache starts to run, or during heavy workload ?
>
> It's during heavy / normal workload.
>
>> If I may have chance to trigger similar oops on my server, that will be
>> much easier. So far I cannot reproduce any oops, neither by rebooting
>> and assemble bcache device by udev rules, nor compose bcache device and
>> run it by bash scripts...
>
> Do you need the line where this happens? It should be possible to get
> the line from the IP: [<ffffffffc04ef62e>] output?
>
This is very helpful. Is it possible to get a kdump crash for the kernel
oops, that will be much more informative :-)
Thanks.
--
Coly Li
next prev parent reply other threads:[~2017-10-23 13:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-23 11:42 bcache: for-next unable to handle kernel NULL pointer dereference at 0000000000000019 Stefan Priebe - Profihost AG
2017-10-23 12:56 ` Coly Li
2017-10-23 12:59 ` Stefan Priebe - Profihost AG
2017-10-23 13:05 ` Coly Li [this message]
2017-10-23 13:16 ` Stefan Priebe - Profihost AG
2017-10-23 14:00 ` Coly Li
2017-10-23 14:26 ` Stefan Priebe - Profihost AG
2017-10-23 14:39 ` Coly Li
2017-10-25 13:26 ` Stefan Priebe - Profihost AG
2017-10-25 14:05 ` Coly Li
2017-10-23 16:48 ` Michael Lyle
2017-10-23 17:49 ` Stefan Priebe - Profihost AG
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=08c770ef-eb09-ed55-a7bb-31b1b97a88d9@coly.li \
--to=i@coly.li \
--cc=linux-bcache@vger.kernel.org \
--cc=mlyle@lyle.org \
--cc=s.priebe@profihost.ag \
/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