https://bugzilla.kernel.org/show_bug.cgi?id=214873 --- Comment #4 from sworddragon2@xxxxxxxxx --- (In reply to Jens Axboe from comment #2) > I don't know what the "see caches" mean in a few spots in the above > text? Dirty kernel cached data - as you described it. (In reply to Jens Axboe from comment #2) > If the device doesn't honor a cache flush (eg "all writes previously > acked are now stable"), then there's nothing the kernel can do about it. In such a case the kernel could still send out all dirty kernel cached data - but the manpage strictly states fsync() would return early here with "The call blocks until the device reports that the transfer has completed.". But in the previous sentences it states it would not. I assume if a storage device falsely claims the transfer has been completed fsync() would still send out dirty kernel cached data if any and blocks until this is done as this would make sense. This ticket is about clarifying this in the manpage, e.g. if this assumption is correct the referenced sentence from above could be changed to "The call blocks until dirty writes are sent out and the device reports that the transfer has completed." or more appropriate if needed. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
