https://bugzilla.kernel.org/show_bug.cgi?id=200681 --- Comment #5 from Theodore Tso (tytso@xxxxxxx) --- 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.
