summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/bin/stackcollapse-report
diff options
context:
space:
mode:
authorFilipe Manana <fdmanana@suse.com>2026-10-02 18:03:06 +0100
committerDavid Sterba <dsterba@suse.com>2026-10-12 19:16:24 +0200
commit599fdbf3e309e0e6227c67629a520c98059e2fff (patch)
treec5851510429030eef804e4d4b0b9cd1d3bdf8aea /tools/perf/scripts/python/bin/stackcollapse-report
parentaad3c3c84f065bbe8644233192ae143a583e4e23 (diff)
downloadlinux-599fdbf3e309e0e6227c67629a520c98059e2fff.tar.gz
linux-599fdbf3e309e0e6227c67629a520c98059e2fff.zip
btrfs: abort transaction on qgroup failures in create_pending_snapshot()
If we get an error when calling one of the qgroup functions, we jump to the 'fail' label without aborting the transaction. This is not a bug as up the call chain (transaction commit path), we will end up aborting the transaction. However having the explicit transaction abort in create_pending_snapshot() allows us to get a stack trace and log message that tells us exactly where we failed, useful for troubleshooting, and also adds consistency since in that function we abort the transaction in every other error path. Reviewed-by: Qu Wenruo <wqu@suse.com> Signed-off-by: Filipe Manana <fdmanana@suse.com> Reviewed-by: David Sterba <dsterba@suse.com> Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-report')
0 files changed, 0 insertions, 0 deletions