From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Andrea Gelmini <andrea.gelmini@gelma.net>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
dgilbert@interlog.com
Subject: Re: BUG: KASAN: slab-out-of-bounds in ses_enclosure_data_process+0x900/0xe50
Date: Fri, 04 Dec 2015 09:09:32 -0800 [thread overview]
Message-ID: <1449248972.27077.7.camel@HansenPartnership.com> (raw)
In-Reply-To: <20151203222004.GA22311@glen>
[-- Attachment #1: Type: text/plain, Size: 1904 bytes --]
On Thu, 2015-12-03 at 23:20 +0100, Andrea Gelmini wrote:
> On Thu, Dec 03, 2015 at 12:59:06PM -0800, James Bottomley wrote:
> > 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.
>
> root@glen:/home/gelma# sg_map -i
> /dev/sg0 /dev/sda ATA Samsung SSD 850 1B6Q
> /dev/sg1 /dev/sr0 HL-DT-ST DVDRAM GU40N QX23
> /dev/sg2 /dev/sdb WD My Passport 0820 1007
> /dev/sg3 WD SES Device 1007
>
> And following Douglas' instructions:
>
> root@glen:/home/gelma# lsscsi -gs
> [0:0:0:0] disk ATA Samsung SSD 850 1B6Q /dev/sda /dev/sg0 1.02TB
> [1:0:0:0] cd/dvd HL-DT-ST DVDRAM GU40N QX23 /dev/sr0 /dev/sg1 -
> [8:0:0:0] disk WD My Passport 0820 1007 /dev/sdb /dev/sg2 2.00TB
> [8:0:0:1] enclosu WD SES Device 1007 - /dev/sg3
>
> root@glen:/home/gelma# sg_ses /dev/sg3
> WD SES Device 1007
> Supported diagnostic pages:
> Supported Diagnostic Pages [sdp] [0x0]
> Short Enclosure Status (SES) [ses] [0x8]
> <unknown> [0x80]
> <unknown> [0x83]
> <unknown> [0x84]
> <unknown> [0x85]
>
>
> Well, if it's better for you, I can give you root access to a machine with this device
> connected to.
Actually, that would be really helpful, since I only have access to one,
very old, enclosure device. My ssh key is
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCnSsL4HoG8CXrJKA2CDAFJi+Ry8EUYgLluzX+zQ21iShnlCelp8djuoe+q+96WX2VGTnxQPJGAYUXNIW+rT9g3g8mgbjLAxYec4AHOgir/LlEBCARHo4SWue9L2if0nl6nLu1PudCQIKM747Pfzj1R4VfWboMU4m6KvkaFgP3rwJkZ96aNHI4ssRDh3EXvlD/vix6DZx0T7UEDpD3icc6ZyA2kmymtGCg1+nAWRTWImsnyhRFTIJvVw+xL7iR6GBoIJND82SpzP13Z95owuLm6QGPWow5Xgp3FLgoh+KezU7qXZh17Wh5ANRbgCNZJDc4fDBhXO+oNZmaU8bc0AW8R
Thanks,
James
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-12-04 17:09 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
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 [this message]
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=1449248972.27077.7.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).