linux-kernel - 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 for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAKYAXd9v_wFg2RQ_R+fYyCJnCbnuMs_VECujOen1GUSGXo3rHw@mail.gmail.com>
Date:	Thu, 13 Oct 2011 09:24:52 +0900
From:	NamJae Jeon <linkinjeon@...il.com>
To:	hirofumi@...l.parknet.co.jp
Cc:	linux-kernel@...r.kernel.org
Subject: RFC : fat : default errors use FAT_ERRORS_CONT instead of FAT_ERRORS_RO.

Hi ogawa.

I found different error exception between linux fat and windows fat.

When fat is currputed by sudden unplug usb device formatted fat, fat
does never change RO partition on windows.

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

Currently when access corrupted file, linux fat change RO parition
from RW. So user no longer do open/write on linux fat.

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

I want to know your opinion.

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