| 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
| ||
|
Message-Id: <201101131842.p0DIgLDG014753@demeter2.kernel.org>
Date: Thu, 13 Jan 2011 18:42:21 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
Theodore Tso <tytso@....edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P1 |P3
CC| |tytso@....edu
--- Comment #1 from Theodore Tso <tytso@....edu> 2011-01-13 18:42:20 ---
This is an old proposal; the challenge which this is that if you do this, we
then have to block any attempts to write to the file system until the dirty bit
has been set in the superblock. It can be done, but it's not been a high
priority to any of the ext3/ext4 developers. Patches to do this will be
accepted. If someone wants more details about how to best do this and is
willing to do the implementation and testing, please let me know.
--
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