linux-kernel - Re: WRITE SAME failed in recent kernels

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] [day] [month] [year] [list]

Date:	Wed, 17 Apr 2013 13:30:34 +0000 (UTC)
From:	Juno Krahn <Juno.Krahn@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Re: WRITE SAME failed in recent kernels

Sune Mølgaard <sune <at> molgaard.org> writes:

> 
> Dear All,
> 
> In the setting of an SSD and an HDD connected to a HighPoint RocketRAID
> 620, I am seeing quite a number of log messages such as:
> 
> Apr 14 06:02:30 jekaterina kernel: [  952.460537] sd 8:0:1:0: [sde]
> Unhandled error code
> Apr 14 06:02:30 jekaterina kernel: [  952.460542] sd 8:0:1:0: [sde]
> Apr 14 06:02:30 jekaterina kernel: [  952.460544] Result: hostbyte=0x05
> driverbyte=0x05
> Apr 14 06:02:30 jekaterina kernel: [  952.460546] sd 8:0:1:0: [sde] CDB:
> Apr 14 06:02:30 jekaterina kernel: [  952.460548] cdb[0]=0x41: 41 00 a8
> c6 fb 78 00 00 18 00
> Apr 14 06:02:30 jekaterina kernel: [  952.460557] end_request: I/O
> error, dev sde, sector 2831612792
> Apr 14 06:02:30 jekaterina kernel: [  952.460566] sde1: WRITE SAME
> failed. Manually zeroing.
> 
> with sde being the regular HDD.
> 
> Now, I am aware that the HighPoint driver, rr62x, isn't part of
> mainline, and thus I have contacted HighPoint Technologies as well, but
> I would like to know how to ascertain whether this is, indeed, a problem
> with their driver, or if it's a problem pertaining to the kernel itself.
> 
> Any help, really, is much appreciated, even if it amounts to "HighPoint
> is to blame", as I would then have that on higher authority than myself.
> 
> Best regards,
> 
> Sune Mølgaard
> 

I have this same problem, resulting in many thousands of kernel messages.
Since WRITE SAME support is not essential, it makes sense that the block
driver should disable this feature when it results in an error.

I am also looking into how the HighPoint driver can be patched to prevent
the block driver from using WRITE SAME. However, it seems probable that
other situations will arise due to driver or hardware issues, and it makes
sense to avoid a potential for a flood of repeated kernel messages,
especially for an optional feature.

Juno Krahn

--
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/