linux-kernel - Re: [PATCH 3/3] faster workaround

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: <470E3B8D.4080002@garzik.org>
Date:	Thu, 11 Oct 2007 11:04:45 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Bernd Schubert <bs@...eap.de>
CC:	Alan Cox <alan@...rguk.ukuu.org.uk>, linux-ide@...r.kernel.org,
	linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/3] faster workaround

Bernd Schubert wrote:
> On Thursday 11 October 2007 16:19:37 Jeff Garzik wrote:
>> 1) Just about the only valid optimization is to ensure that only the
>> write path must be limited to small chunks, not both read- and
>> write-paths.  Tejun had a patch to do this a long time ago, but it's an
>> open question whether the large amount of code is worth it for a rare
>> combination.
> 
> How large? This patch is rather small? Where can I find it?

http://home-tj.org/wiki/index.php/Sil_m15w

> The problem came up, when 200GB drives were replaced by *newer* 250GB drives 
> (well maybe not the newest, no idea were they came from).
> 
> Anyway, I'm testing for more than 24h already and didn't observe any data 
> corruption as without the patch. I know this is only an obersavation and no 
> definite prove...
> Also, this is with 3114, maybe this chip behaves a bit different than 3112?

3114 + new SATA drive is definitely a new one for us.

It would help to (a) use the latest kernel, (b) post your .config with 
the latest kernel, (c) post lspci booted into latest kernel, and (d) 
post dmesg booted into latest kernel.

	Jeff


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