linux-ext4 - [Bug 26642] New: Automatically clean dirty bit on ext2/ext4-without-journal file systems

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

Date:	Thu, 13 Jan 2011 15:18:25 GMT
From:	bugzilla-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 26642] New: Automatically clean dirty bit on
 ext2/ext4-without-journal file systems

https://bugzilla.kernel.org/show_bug.cgi?id=26642

           Summary: Automatically clean dirty bit on
                    ext2/ext4-without-journal file systems
           Product: File System
           Version: 2.5
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: enhancement
          Priority: P1
         Component: ext4
        AssignedTo: fs_ext4@...nel-bugs.osdl.org
        ReportedBy: t.artem@...lcity.com
        Regression: No


In ext2/journalless ext4 if you forget to umount the FS before
rebooting/powering down PC you'll have to run fsck on a next boot. That's
obvious.

However we can easily avoid fsck'ing if we clean the dirty bit about a certain
timeout (I suggest a configurable 300 seconds value) and only after dirty
buffers have been flushed to the disk. If we write to the disk again, then this
bit should be set again, of course.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html