diff options
author | 2022-06-13 15:09:48 -0400 | |
---|---|---|
committer | 2022-07-25 17:45:34 +0200 | |
commit | f31f09f6be1c6c1a673e0566e258281a7bbaaa51 (patch) | |
tree | 6b85adc65b4be2c3a4fed86d22d178a3df53637c /tools/perf/scripts/python/syscall-counts.py | |
parent | btrfs: add tracepoints for ordered extents (diff) | |
download | linux-dev-f31f09f6be1c6c1a673e0566e258281a7bbaaa51.tar.xz linux-dev-f31f09f6be1c6c1a673e0566e258281a7bbaaa51.zip |
btrfs: tree-log: make the return value for log syncing consistent
Currently we will return 1 or -EAGAIN if we decide we need to commit
the transaction rather than sync the log. In practice this doesn't
really matter, we interpret any !0 and !BTRFS_NO_LOG_SYNC as needing to
commit the transaction. However this makes it hard to figure out what
the correct thing to do is.
Fix this up by defining BTRFS_LOG_FORCE_COMMIT and using this in all the
places where we want to force the transaction to be committed.
CC: stable@vger.kernel.org # 5.15+
Reviewed-by: Filipe Manana <fdmanana@suse.com>
Signed-off-by: Josef Bacik <josef@toxicpanda.com>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'tools/perf/scripts/python/syscall-counts.py')
0 files changed, 0 insertions, 0 deletions