| 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: <200911091454.nA9EsPlh013795@demeter.kernel.org> Date: Mon, 9 Nov 2009 14:54:25 GMT From: bugzilla-daemon@...zilla.kernel.org To: linux-ext4@...r.kernel.org Subject: [Bug 14354] Bad corruption with 2.6.32-rc1 and upwards http://bugzilla.kernel.org/show_bug.cgi?id=14354 --- Comment #185 from Chris Mason <chris.mason@...cle.com> 2009-11-09 14:54:13 --- Good point on the symlink code we must be copying the null already. There's another strange one I hit at mount time last week but forgot to include. It could be noise from earlier debugging runs of the patch that left readonly pages setting around, but I think if I squint really it makes sense. During mounts and remounts, ext4 will mess around with the flags on the journal super. I don't see exactly where the buffer is logged or prepared...most of the callers of jbd2_journal_clear_features look like they need a bigger audit to me. Does anyone know the perf cost of forcing the page ro/rw? I'm looking at integrating it into a CONFIG_DEBUG_CSUMS for btrfs. For any individual page it shouldn't happen too often, but we'd be hammering on it pretty good during a commit. -- Configure bugmail: http://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