| 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
| ||
|
Date: Tue, 08 Aug 2006 15:06:21 +0400 From: Edward Shishkin <edward@...esys.com> To: Matthias Andree <matthias.andree@....de> CC: Hans Reiser <reiser@...esys.com>, reiserfs-list@...esys.com, linux-kernel@...r.kernel.org Subject: Re: the " 'official' point of view" expressed by kernelnewbies.org regarding reiser4 inclusion Matthias Andree wrote: > [stripping Cc: list] > > On Thu, 03 Aug 2006, Edward Shishkin wrote: > > >>>What kind of forward error correction would that be, >> >>Actually we use checksums, not ECC. If checksum is wrong, then run >>fsck - it will remove the whole disk cluster, that represent 64K of >>data. > > > Well, that's quite a difference... > > >>Checksum is checked before unsafe decompression (when trying to >>decompress incorrect data can lead to fatal things). > > > Is this sufficient? How about corruptions that lead to the same checksum > and can then confuse the decompressor? It is a multiplication of two unlikely events: fs corruption and 32-hash collision. Paranoid people can assign zlib-based transform plugin: afaik everything is safe there. Is the decompressor safe in that > it does not scribble over memory it has not allocated? > yes - 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