From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: "jianchao.wang" <jianchao.w.wang@oracle.com>
Cc: jejb@linux.ibm.com, martin.petersen@oracle.com,
"linux-scsi\@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Junxiao Bi <junxiao.bi@oracle.com>,
diego.gonzalez@oracle.com
Subject: Re: [BUG] scsi: ses: out of bound accessing in ses_enclosure_data_process
Date: Mon, 18 Mar 2019 01:01:58 -0400 [thread overview]
Message-ID: <yq1k1gwkc6x.fsf@oracle.com> (raw)
In-Reply-To: <78dd3eca-7e8a-72f9-07f9-e2c7cc4569b0@oracle.com> (jianchao wang's message of "Thu, 14 Mar 2019 11:19:31 +0800")
Jianchao,
> When our customer probe the lpfc devices, they encountered odd memory
> corruption issues, and we get 'out of bound' access warning at
> following position after open KASAN
Please provide the output of:
# sg_ses -p 1 /dev/sgN
# sg_ses -p 7 /dev/sgN
for the enclosure device in question.
--
Martin K. Petersen Oracle Linux Engineering
WARNING: multiple messages have this Message-ID (diff)
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: "jianchao.wang" <jianchao.w.wang@oracle.com>
Cc: jejb@linux.ibm.com, martin.petersen@oracle.com,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Junxiao Bi <junxiao.bi@oracle.com>,
diego.gonzalez@oracle.com
Subject: Re: [BUG] scsi: ses: out of bound accessing in ses_enclosure_data_process
Date: Mon, 18 Mar 2019 01:01:58 -0400 [thread overview]
Message-ID: <yq1k1gwkc6x.fsf@oracle.com> (raw)
In-Reply-To: <78dd3eca-7e8a-72f9-07f9-e2c7cc4569b0@oracle.com> (jianchao wang's message of "Thu, 14 Mar 2019 11:19:31 +0800")
Jianchao,
> When our customer probe the lpfc devices, they encountered odd memory
> corruption issues, and we get 'out of bound' access warning at
> following position after open KASAN
Please provide the output of:
# sg_ses -p 1 /dev/sgN
# sg_ses -p 7 /dev/sgN
for the enclosure device in question.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2019-03-18 5:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 3:19 [BUG] scsi: ses: out of bound accessing in ses_enclosure_data_process jianchao.wang
2019-03-18 3:13 ` jianchao.wang
2019-03-18 4:17 ` Junxiao Bi
2019-03-18 5:01 ` Martin K. Petersen [this message]
2019-03-18 5:01 ` Martin K. Petersen
2019-03-18 5:09 ` jianchao.wang
2019-03-18 15:22 ` Ewan D. Milne
2019-03-19 2:41 ` jianchao.wang
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=yq1k1gwkc6x.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=diego.gonzalez@oracle.com \
--cc=jejb@linux.ibm.com \
--cc=jianchao.w.wang@oracle.com \
--cc=junxiao.bi@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.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.