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: <201101132347.p0DNl3sW025661@demeter1.kernel.org>
Date:	Thu, 13 Jan 2011 23:47:03 GMT
From:	bugzilla-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 26642] Automatically clean dirty bit on
 ext2/ext4-without-journal file systems

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


Andreas Dilger <adilger.kernelbugzilla@...ger.ca> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |adilger.kernelbugzilla@...g
                   |                            |er.ca




--- Comment #2 from Andreas Dilger <adilger.kernelbugzilla@...ger.ca>  2011-01-13 23:46:56 ---
I would also suggest looking at the per-group dirty bit that Val Henson
developed, maybe 1.5 years ago.  This allowed e2fsck to limit its boot-time
scanning to only the small subset of groups/inodes that were modified shortly
before the crash.

I don't know how close to production-ready that code was, but it was at least
at the working prototype stage.  Some changes and updates are probably needed
(e.g. changing the per-group flag value to avoid conflicting with other
assigned flags) before using it on a newer kernel with ext4.

-- 
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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ