linux-ext4 - [Bug 70121] Increasing efficiency of full data journaling

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 07 Mar 2014 15:42:13 +0000
From:	bugzilla-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 70121] Increasing efficiency of full data journaling

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

--- Comment #8 from sworddragon2@....com ---
Thanks for the information :)

In this case full data journaling seems not to make all the things I thought it
does. Maybe my last tests are just too long ago. But this means also that I
still can have data loss if the system crashes while writing to the disk. It
would be really nice if the filesystem would provide such a mechanism in the
future.

> How does the file system know that the file has "successfully been
> written"?

Does the filesystem really not know if the file is complete? If this could be
achieved a transaction safety should be not the problem here.

> If you think it can be done, plesae submit patches.  :-)

Sure I would if:

- My experience with C would be a little higher.
- Or at least if I would have the time to make a deeper look into the
sourcecode and the coding rules for the kernel.

I have posted the last few years many hundred bugs/feature requests in ~100
different projects and am still doing this many times a week. But don't worry,
they don't have so many bogus reports as I'm reporting here :)
The kernel is really a difficult place if you are not directly involved with it
but want to improve something. But some of my tickets here had already success.
Also I'm programming on own projects and this all together consumes much time.

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