linux-kernel - Re: fat: changed filesystem dirty bit behavior

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] [day] [month] [year] [list]

Message-ID: <5718D49B.3090908@gmail.com>
Date:	Thu, 21 Apr 2016 09:24:43 -0400
From:	"Austin S. Hemmelgarn" <ahferroin7@...il.com>
To:	Anssi Hannula <anssi.hannula@...wise.fi>,
	OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>,
	linux-fsdevel@...r.kernel.org
Cc:	Oleksij Rempel <bug-track@...her-privat.net>,
	linux-kernel@...r.kernel.org
Subject: Re: fat: changed filesystem dirty bit behavior

On 2016-04-21 09:09, Anssi Hannula wrote:
> Hi all!
>
> Starting with commit b88a105802e9aeb [1] ("fat: mark fs as dirty on
> mount and clean on umount") FAT(32) filesystems are now marked as
> "dirty" on mount and clean on unmount.
>
> The commit message says that this is similar to Win 7 behavior - "Win 7,
> set dirty flag on first write and remove it on umount".
> However, I have been unable to coerce my Windows 7 system to set this
> flag on a FAT32 filesystem, when tested both with portable (USB) and
> fixed disks. Have they maybe changed this with an update, or does
> someone else still see this bit set on Win7 or later?
>
> This change is a bit problematic on a legacy embedded application I'm
> working on, as the user interface doesn't have any separate
> eject/unmount button for a USB stick - it relies on the user not
> unplugging the stick while a data transfer is in progress.
> So, when the system is upgraded to a modern vanilla kernel version, this
> bit is set when the USB stick is unplugged, causing Windows to always
> prompt whether to scan and fix the drive, which is annoying/confusing
> for users.
>
> Would a patch to add a filesystem option to restore the previous (and
> seemingly Win7) behavior be accepted?
>
> Or is this a case where the application is just considered to be broken?
> (as setting the dirty bit seems technically correct, even if Windows
> doesn't do it)
>
> Or anything else I'm missing?
Based on some recent testing I did on Windows 10, and assuming it has 
similar behavior to the current Windows 7 behavior (which isn't a far 
stretch, they actually back-ported a lot of the lower level stuff that 
they reasonably can), it appears to set the dirty bit only when 
something is actually written to on the disk, which makes some sense, 
because the filesystem really isn't dirty until we've written something 
  to it.