linux-ext4 - [Bug 200681] [inline_data] read() does not see what write() has just written through different FD in the same thread

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: <bug-200681-13602-cS23GlRKOE@https.bugzilla.kernel.org/>
Date:   Wed, 01 Aug 2018 16:04:34 +0000
From:   bugzilla-daemon@...zilla.kernel.org
To:     linux-ext4@...nel.org
Subject: [Bug 200681] [inline_data] read() does not see what write() has just
 written through different FD in the same thread

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

--- Comment #5 from Theodore Tso (tytso@....edu) ---
There are in fact a number of ways that inline_data is broken for files --- in
particular when a file transitions from a small file that fits inside the
inode, to a large file.   However, when I looked at your reproducer, it did
*not* appear to be one of the cases which I would have expected to be
problematic.

So when I tried it in my KVM framework, I was not surprised when it worked for
me.   That being said, as I've said, there are definitely problems with
inline_data --- there is a reason why it is not enabled by default!

(For example, generic/477 is broken for the inline case, which can be easily
seen by running "kvm-xfstests -c inline generic/477".  For another, there are
some cases where if you crash immediately after a inline->regular conversion,
the file contents might not be correct.)

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