linux-ext4 - [Bug 13964] ext4: panic causes lost data in git

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>] [day] [month] [year] [list]

Date:	Tue, 25 May 2010 18:02:54 GMT
From:	bugzilla-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 13964] ext4: panic causes lost data in git

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


Eric Sandeen <sandeen@...hat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sandeen@...hat.com




--- Comment #6 from Eric Sandeen <sandeen@...hat.com>  2010-05-25 18:02:53 ---
Jesse, are you still running with data=writeback (as comment nr. 1 seemed to
indicate, since you said you would -try- data=ordered...) - data=writeback is
just not safe at all for anybody, anywhere, any time, unless you plan to
recreate all data post-crash.

With default mount options (which includes data=ordered) do you still see this
problem on upstream kernels?

In the end, though, you have to realize that buffered data which is not synced
to disk -will- be lost on a crash.  This is true for all filesystems, though
the window of "opportunity" may differ....

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