lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1449177604.2187.20.camel@HansenPartnership.com>
Date:	Thu, 03 Dec 2015 13:20:04 -0800
From:	James Bottomley <James.Bottomley@...senPartnership.com>
To:	dgilbert@...erlog.com
Cc:	Andrea Gelmini <andrea.gelmini@...ma.net>,
	linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org
Subject: Re: BUG: KASAN: slab-out-of-bounds in
 ses_enclosure_data_process+0x900/0xe50

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@...n:/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


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ