linux-kernel - Re: RFC : fat : default errors use FAT_ERRORS_CONT instead of FAT_ERRORS

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: <13498.1318467461@turing-police.cc.vt.edu>
Date:	Wed, 12 Oct 2011 20:57:41 -0400
From:	Valdis.Kletnieks@...edu
To:	NamJae Jeon <linkinjeon@...il.com>
Cc:	hirofumi@...l.parknet.co.jp, linux-kernel@...r.kernel.org
Subject: Re: RFC : fat : default errors use FAT_ERRORS_CONT instead of FAT_ERRORS_RO.

On Thu, 13 Oct 2011 09:24:52 +0900, NamJae Jeon said:

> It said windows fat provide a chance that continuously access
> partition except corrupted file.

It also gives you a chance to make things worse by continuing to write to the
device.  If you force it RO at the first sign of trouble, maybe you lose a few
blocks of one file.  If you keep writing to it, creating new files, erasing
files, and so on, pretty soon your corrupted filesystem is even more corrupted.

> I suggest that the default errors of linux fat use FAT_ERRORS_CONT
> instead of FAT_ERRORS_RO.

And what user benefit does that give?  If you keep going, they won't
realize their device is corrupted, and won't have any reason to *fix* the
filesystem.

Content of type "application/pgp-signature" skipped