linux-ext4 - [Bug 43354] Corruption on a small loopback ext4 file system with Linux 3.4

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: <20120608174639.7F0BB1205DA@bugzilla.kernel.org>
Date:	Fri,  8 Jun 2012 17:46:39 +0000 (UTC)
From:	bugzilla-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 43354] Corruption on a small loopback ext4 file system with
 Linux 3.4

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





--- Comment #4 from Eric Sandeen <sandeen@...hat.com>  2012-06-08 17:46:39 ---
Hm, wait - drop caches _after_ unmount is required?  Ok that's even weirder
(and scarier - especially since it's after a sync)

And - on further testing, ext2 & ext3 fail too.  Yikes.

It also seems to happen only on loopback; a real device is fine.

And, loopback fails whether it's hosted on ext4 or xfs.  So something generic
broke here...

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