https://bugzilla.kernel.org/show_bug.cgi?id=200871
--- Comment #11 from Stathis Maneas (sman...@cs.toronto.edu) --- Considering the fact that the operation modifies the entry's inode and that fsync is invoked at the end of the program so that all modifications persist, then a new inode will eventually be written at a new location on disk. The attached files aim to capture this write operation and drop it, also returning an error to the upper layers. Could you please let me know how should I help you reproduce this issue? I would definitely be willing to provide more files/information if necessary. -- You are receiving this mail because: You are watching the assignee of the bug. _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
