FROMGIT: mm: slub: Print the broken data before restoring them

Previously, the restore occurred after printing the object in slub.
After commit 47d911b0 ("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>

Link: https://lore.kernel.org/linux-mm/20250226081206.680495-1-hyesoo.yu@samsung.com/
(cherry picked from commit 149190ef8008ab533d6967425deb065abb788f02
 https://git.kernel.org/pub/scm/linux/kernel/git/vbabka/slab.git

 for-6.15/fixes-cleanups)
Bug: 399511949
Change-Id: I1445cecb3cfc5866dedde2c3a015a2e8ade2c41f
Signed-off-by: Hyesoo Yu <hyesoo.yu@samsung.com>