From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: dgilbert@interlog.com
Cc: Andrea Gelmini <andrea.gelmini@gelma.net>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: BUG: KASAN: slab-out-of-bounds in ses_enclosure_data_process+0x900/0xe50
Date: Thu, 03 Dec 2015 13:20:04 -0800 [thread overview]
Message-ID: <1449177604.2187.20.camel@HansenPartnership.com> (raw)
In-Reply-To: <5660B015.5050804@interlog.com>
On Thu, 2015-12-03 at 16:11 -0500, Douglas Gilbert wrote:
> On 15-12-03 03:59 PM, James Bottomley wrote:
> > On Thu, 2015-12-03 at 21:36 +0100, Andrea Gelmini wrote:
> >> On Wed, Dec 02, 2015 at 02:58:21PM -0800, James Bottomley wrote:
> >>> On Tue, 2015-12-01 at 21:20 +0100, Andrea Gelmini wrote:
> >>> OK, this looks like some type of problem with a USB enclosure. It's
> >>> probably misreporting something in the mode pages. can you run sg_ses
> >>> on whatever /dev/sg<n> the enclosure turns up as?
> >>
> >>
> >> root@glen:/tmp/report# cat sg_ses_usb_hd.txt
> >> WD My Passport 0820 1007
> >> disk device (not an enclosure)
> >> Supported diagnostic pages:
> >> Supported Diagnostic Pages [sdp] [0x0]
> >> Short Enclosure Status (SES) [ses] [0x8]
> >> <unknown> [0x80]
> >> <unknown> [0x83]
> >> <unknown> [0x84]
> >> <unknown> [0x85]
> >
> > Actually, I'm afraid that's the wrong device; it's the disk not the
> > enclosure (that's why sg_ses says not an enclosure)
> >
> > If you do
> >
> > sg_map -i
> >
> > in your system, you should see something with an inquiry string like
> > enclosure. It's the /dev/sg<n> of that you need to run sg_ses on.
>
> Or use lsscsi like this and look for lines with 'enclosu' in
> its output:
> # lsscsi -gs
> [3:0:0:0] disk ATA ST3160812AS D /dev/sda /dev/sg0 160GB
> [6:0:0:0] disk SEAGATE ST200FM0073 0007 /dev/sdb /dev/sg1 200GB
> [6:0:1:0] enclosu Areca ARC-802801.13.1D 0113 - /dev/sg2 -
>
> Then:
> # sg_ses /dev/sg2
> Areca ARC-802801.13.1D 0113
> Supported diagnostic pages:
> Supported Diagnostic Pages [sdp] [0x0]
> Configuration (SES) [cf] [0x1]
> Enclosure Status/Control (SES) [ec,es] [0x2]
> String In/Out (SES) [str] [0x4]
> Threshold In/Out (SES) [th] [0x5]
> Element Descriptor (SES) [ed] [0x7]
> Additional Element Status (SES-2) [aes] [0xa]
> Supported SES Diagnostic Pages (SES-2) [ssp] [0xd]
> Download Microcode (SES-2) [dm] [0xe]
> Subenclosure Nickname (SES-2) [snic] [0xf]
> Protocol Specific (SAS transport) [] [0x3f]
Actually I need a hex dump of pages 1 7 and 0xa ... how do you get that?
Thanks,
James
next prev parent reply other threads:[~2015-12-03 21:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 20:20 BUG: KASAN: slab-out-of-bounds in ses_enclosure_data_process+0x900/0xe50 Andrea Gelmini
2015-12-02 22:58 ` James Bottomley
2015-12-03 20:36 ` Andrea Gelmini
2015-12-03 20:59 ` James Bottomley
2015-12-03 21:11 ` Douglas Gilbert
2015-12-03 21:20 ` James Bottomley [this message]
2015-12-03 22:20 ` Andrea Gelmini
2015-12-04 16:58 ` Ewan Milne
2015-12-04 19:16 ` James Bottomley
2015-12-04 20:40 ` Ewan Milne
2015-12-04 17:09 ` James Bottomley
2015-12-04 17:46 ` Andrea Gelmini
2015-12-04 19:04 ` James Bottomley
2015-12-03 14:20 Pavel Tikhomirov
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=1449177604.2187.20.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=andrea.gelmini@gelma.net \
--cc=dgilbert@interlog.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 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).