diff options
| author | Filipe Manana <fdmanana@suse.com> | 2026-02-19 15:37:59 +0000 |
|---|---|---|
| committer | David Sterba <dsterba@suse.com> | 2026-04-07 18:55:58 +0200 |
| commit | d821d4f6fb804d2579b4523e591cb6dd03a49b86 (patch) | |
| tree | 58c67dc9c131f54a955f6d70ef5708b72897b0a7 /tools/perf/scripts/python | |
| parent | 1899d9b09d171834a950254ad21718618e5c7fd6 (diff) | |
btrfs: stop printing condition result in assertion failure messages
It's useless to print the result of the condition, it's always 0 if the
assertion is triggered, so it doesn't provide any useful information.
Examples:
assertion failed: cb->bbio.bio.bi_iter.bi_size == disk_num_bytes :: 0, in inode.c:9991
assertion failed: folio_test_writeback(folio) :: 0, in subpage.c:476
So stop printing that, it's always ":: 0" for any assertion triggered
(except for conditions that are just an identifier).
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')
0 files changed, 0 insertions, 0 deletions
