mirror of
https://github.com/Zygo/bees.git
synced 2025-05-17 21:35:45 +02:00
tempfile: remove old comments about fsync and deadlock bugs
I was never able to prove a connection between fsync() and deadlock bugs. There were too many deadlock bugs to be able to isolate a bug that is triggered specifically by fsync. Update the comment (which has been unchanged since kernel 4.14). We still may want to do fsync() on temporary files someday, but there's a full internal API rewrite between here and there. Signed-off-by: Zygo Blaxell <bees@furryterror.org>
This commit is contained in:
parent
459071597b
commit
1e7dbc6f97
@ -598,13 +598,12 @@ BeesTempFile::make_copy(const BeesFileRange &src)
|
||||
}
|
||||
BEESCOUNTADD(tmp_copy_ms, copy_timer.age() * 1000);
|
||||
|
||||
// We seem to get lockups without this!
|
||||
if (did_block_write) {
|
||||
#if 0
|
||||
// Is this fixed by "Btrfs: fix deadlock between dedup on same file and starting writeback"?
|
||||
// No.
|
||||
// Is this fixed in kernel 4.14.34?
|
||||
// No.
|
||||
// There were a lot of kernel bugs leading to lockups.
|
||||
// Most of them are fixed now.
|
||||
// Unnecessary sync makes us slow, but maybe it has some robustness utility.
|
||||
// TODO: make this configurable.
|
||||
bees_sync(m_fd);
|
||||
#endif
|
||||
}
|
||||
|
Loading…
x
Reference in New Issue
Block a user