linux-ext4 - [Bug 200693] New: fsync() in the latest kernel (4.15.x ) Broken ????

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

Date:   Tue, 31 Jul 2018 13:51:57 +0000
From:   bugzilla-daemon@...zilla.kernel.org
To:     linux-ext4@...nel.org
Subject: [Bug 200693] New: fsync() in the latest kernel (4.15.x ) Broken ????

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

            Bug ID: 200693
           Summary: fsync() in the latest kernel (4.15.x ) Broken ????
           Product: File System
           Version: 2.5
    Kernel Version: 4.15.0-29-generic
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: ext4
          Assignee: fs_ext4@...nel-bugs.osdl.org
          Reporter: caron.wills@...il.com
        Regression: No

So this is a simple one, if I run the following code on Ubuntu 18.04
(4.15.0-29-generic ) and against 
Ubuntu 16.04 ( 4.4.0-87-generic) I get two different results ; The question is
why? It seems that 
fsync may be broken in the latest kernel and may well be broken as early as
4.10 ? 
This has huge implications around performance sensitive applications like
mysql. 
(Yes I know it can be turned off in mysql but thats only any good if you like
your databases corrupted).

4.4.0-87-generic - # time ./fsync 
real 0m7.537s <-----
user 0m0.000s
sys 0m1.060s <-----

-- 
You are receiving this mail because:
You are watching the assignee of the bug.