| 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
| ||
|
Date: Mon, 26 Oct 2009 19:13:15 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
Linus Torvalds <torvalds@...ux-foundation.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |torvalds@...ux-foundation.o
| |rg
--- Comment #119 from Linus Torvalds <torvalds@...ux-foundation.org> 2009-10-26 19:13:13 ---
It seems to be only after an unclean shutdown for me, judging by some judicious
grepping of /var/log/messgaes. At least the ext4 error messages in dmesg only
seem to happen when I don't see the line "Kernel logging (proc) stopped." in
the messages file before the new boot.
Of course, maybe the problem is caused by - or even just made visible by - not
the unclean shutdown itself, but the fsck or the journal replay which is just
triggered by the unclean shutdown. IOW, it could be secondary damage. That
sounds unlikely, though.
I dunno. As mentioned, I don't think that I was doing anything particularly
write-heavy when I forced the unclean shutdown.
--
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