From: "Ewan D. Milne" <emilne@redhat.com>
To: "chenxiang (M)" <chenxiang66@hisilicon.com>,
"James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Ming Lei <ming.lei@redhat.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
John Garry <john.garry@huawei.com>,
Linuxarm <linuxarm@huawei.com>
Subject: Re: DIF/DIX issue related to config CONFIG_SCSI_MQ_DEFAULT
Date: Tue, 27 Nov 2018 15:22:15 -0500 [thread overview]
Message-ID: <0fbf532cf75e23ad70367d66c53f2de7819aa71a.camel@redhat.com> (raw)
In-Reply-To: <5d9bf51d-1ef9-b948-2168-9e7526d77225@hisilicon.com>
On Tue, 2018-11-27 at 17:55 +0800, chenxiang (M) wrote:
> [ 629.210506] Unable to handle kernel paging request at virtual address
> 0000ffff8027e048
> [ 629.210506] Unable to handle kernel paging request at virtual address
> 0000ffff8027e048
> ...
> [ 629.380218] pc : deadline_remove_request+0x2c/0xd0
> [ 629.380218] pc : deadline_remove_request+0x2c/0xd0
> [ 629.389799] lr : dd_dispatch_request+0x184/0x1e0
> [ 629.389799] lr : dd_dispatch_request+0x184/0x1e0
> [ 629.399031] sp : ffff0000275a3aa0
> [ 629.399031] sp : ffff0000275a3aa0
> [ 629.405651] x29: ffff0000275a3aa0 x28: ffff8027dc230d40
> [ 629.405651] x29: ffff0000275a3aa0 x28: ffff8027dc230d40
> [ 629.416278] x27: 0000000000000001 x26: ffff8027dc230d40
> [ 629.416278] x27: 0000000000000001 x26: ffff8027dc230d40
> [ 629.426903] x25: 0000000000000000 x24: ffff0000094f1000
> [ 629.426903] x25: 0000000000000000 x24: ffff0000094f1000
> [ 629.437529] x23: ffff8027a1e1d140 x22: 0000000000000006
> [ 629.437529] x23: ffff8027a1e1d140 x22: 0000000000000006
> [ 629.448155] x21: ffff7e009ec69842 x20: ffff8027a1e1d100
> [ 629.448155] x21: ffff7e009ec69842 x20: ffff8027a1e1d100
> [ 629.458781] x19: ffff8027a1e1d100 x18: 0000000000000000
> [ 629.458781] x19: ffff8027a1e1d100 x18: 0000000000000000
> [ 629.469406] x17: 000000009e8c9c80 x16: 00000027a3272000
> [ 629.469406] x17: 000000009e8c9c80 x16: 00000027a3272000
> [ 629.480032] x15: ffff7e009fff9534 x14: ffff7e009ec698c0
> [ 629.480032] x15: ffff7e009fff9534 x14: ffff7e009ec698c0
> [ 629.490658] x13: ffff7e009ec69880 x12: 0000000000000009
> [ 629.490658] x13: ffff7e009ec69880 x12: 0000000000000009
> [ 629.501284] x11: 0000000000000000 x10: ffff8027a7c03560
> [ 629.501284] x11: 0000000000000000 x10: ffff8027a7c03560
> [ 629.511910] x9 : ffff8027a7c007b8 x8 : 0000000000000007
> [ 629.511910] x9 : ffff8027a7c007b8 x8 : 0000000000000007
> [ 629.522535] x7 : ffff8027a7c011c8 x6 : 0000000000000000
> [ 629.522535] x7 : ffff8027a7c011c8 x6 : 0000000000000000
> [ 629.533161] x5 : 0000000000000000 x4 : 0000ffff8027e040
> [ 629.533161] x5 : 0000000000000000 x4 : 0000ffff8027e040
> [ 629.543787] x3 : ffff8027a1e20040 x2 : ffff8027da87f6a0
> [ 629.543787] x3 : ffff8027a1e20040 x2 : ffff8027da87f6a0
> [ 629.554413] x1 : ffff8027a1e1d140 x0 : ffff8027a1e1d160
> [ 629.554413] x1 : ffff8027a1e1d140 x0 : ffff8027a1e1d160
I don't have an ARM architecture machine, but the faulting
address looks like it may have been loaded from a corrupted
pointer value (0000ffff8027e048 instead of ffff8027e048----)
The code in question uses some list primitives, were there any
warning messages about list corruption prior to the crash?
-Ewan
next prev parent reply other threads:[~2018-11-27 20:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 9:55 DIF/DIX issue related to config CONFIG_SCSI_MQ_DEFAULT chenxiang (M)
2018-11-27 13:08 ` Ming Lei
2018-11-28 3:37 ` chenxiang (M)
2018-11-29 18:17 ` Ming Lei
[not found] ` <6c573f36-60d8-0631-e9ac-dacd72f6c8ad@hisilicon.com>
2018-11-29 0:54 ` Ming Lei
2018-11-30 1:19 ` Ming Lei
2018-11-30 11:26 ` John Garry
2018-12-04 3:55 ` Martin K. Petersen
[not found] ` <45193ec6-6398-3953-4833-88ca2057971a@huawei.com>
2018-12-05 2:22 ` Martin K. Petersen
2018-12-05 15:27 ` John Garry
2018-12-06 4:22 ` Martin K. Petersen
2018-12-06 17:33 ` John Garry
2018-12-07 3:20 ` Martin K. Petersen
2018-12-05 2:56 ` Martin K. Petersen
2018-11-27 20:22 ` Ewan D. Milne [this message]
2018-11-28 3:11 ` chenxiang (M)
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=0fbf532cf75e23ad70367d66c53f2de7819aa71a.camel@redhat.com \
--to=emilne@redhat.com \
--cc=chenxiang66@hisilicon.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=john.garry@huawei.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=martin.petersen@oracle.com \
--cc=ming.lei@redhat.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;
as well as URLs for NNTP newsgroup(s).