| 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: Thu, 13 Oct 2011 16:35:29 +0900 From: NamJae Jeon <linkinjeon@...il.com> To: OGAWA Hirofumi <hirofumi@...l.parknet.co.jp> Cc: linux-kernel@...r.kernel.org Subject: Re: RFC : fat : default errors use FAT_ERRORS_CONT instead of FAT_ERRORS_RO. 2011/10/13 OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>: > NamJae Jeon <linkinjeon@...il.com> writes: > >> 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. > > I think it is dangerous, and the default should be safer side. > > If driver noticed the corruption, it means FS is not unknown state > anymore. Any files/directories are possibly corrupted. > > Even if you change the file that seems to be uncorrupted, it may make FS > unrecoverable more. (e.g. lose all data in worst case) Hi ogawa. Thanks for your reply. I follow your opinion. > > Thanks. > -- > OGAWA Hirofumi <hirofumi@...l.parknet.co.jp> > -- 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