linux-kernel - Re: New filesystem for Linux

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: <Pine.LNX.4.64.0611051916030.11107@artax.karlin.mff.cuni.cz>
Date:	Sun, 5 Nov 2006 19:18:01 +0100 (CET)
From:	Mikulas Patocka <mikulas@...ax.karlin.mff.cuni.cz>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Albert Cahalan <acahalan@...il.com>, kangur@...com.net,
	linux-kernel@...r.kernel.org
Subject: Re: New filesystem for Linux

On Sun, 5 Nov 2006, Alan Cox wrote:

> Ar Sul, 2006-11-05 am 18:18 +0100, ysgrifennodd Mikulas Patocka:
>> Should IDE driver read back parameters after writing them before issuing
>> the command? That should fix this problem. (except when command
>>  is written badly)
>
> For "normal" usage I suspect not - the lack of ECC memory is probably
> more serious as is the lack of PCI parity checking.

I meant for the corruption on IDE cable ... I have 5 UDMA CRC errors over 
8 years of usage, so I can imagine someone could have command parameters 
corrupted too --- or are they transmitted in a more reliable way?

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