diff options
author | Hyesoo Yu <hyesoo.yu@samsung.com> | 2025-02-26 17:12:00 +0900 |
---|---|---|
committer | Vlastimil Babka <vbabka@suse.cz> | 2025-03-04 08:53:50 +0100 |
commit | ed5ec2e952595a469eae1f6dce040737359b6da2 (patch) | |
tree | 63a7eb50fcc34de3895f812247b784bf7f046ba6 /tools/perf/scripts/python/syscall-counts.py | |
parent | 539f552892b757ca7a9eb1ba34f5be3c0a947f59 (diff) |
mm: slub: Print the broken data before restoring them
Previously, the restore occurred after printing the object in slub.
After commit 47d911b02cbe ("slab: make check_object() more consistent"),
the bytes are printed after the restore. This information about the bytes
before the restore is highly valuable for debugging purpose.
For instance, in a event of cache issue, it displays byte patterns
by breaking them down into 64-bytes units. Without this information,
we can only speculate on how it was broken. Hence the corrupted regions
should be printed prior to the restoration process. However if an object
breaks in multiple places, the same log may be output multiple times.
Therefore the slub log is reported only once to prevent redundant printing,
by sending a parameter indicating whether an error has occurred previously.
Signed-off-by: Hyesoo Yu <hyesoo.yu@samsung.com>
Reviewed-by: Harry Yoo <harry.yoo@oracle.com>
Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
Diffstat (limited to 'tools/perf/scripts/python/syscall-counts.py')
0 files changed, 0 insertions, 0 deletions