[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210520013539.3733631-1-swboyd@chromium.org>
Date: Wed, 19 May 2021 18:35:36 -0700
From: Stephen Boyd <swboyd@...omium.org>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: linux-kernel@...r.kernel.org, Christoph Lameter <cl@...ux.com>,
Pekka Enberg <penberg@...nel.org>,
David Rientjes <rientjes@...gle.com>,
Joonsoo Kim <iamjoonsoo.kim@....com>,
Vlastimil Babka <vbabka@...e.cz>, linux-mm@...ck.org
Subject: [PATCH 0/3] slub: Print non-hashed pointers in slub debugging
I was doing some debugging recently and noticed that my pointers were
being hashed while slub_debug was on the kernel commandline. Let's make
the prints in here meaningful in that case by pushing %px throughout.
Alternatively, we could force on no_hash_pointers if slub_debug is on
the commandline. Maybe that would be better?
The final patch is just something else I noticed while looking at the
code. The message argument is never used so the debugging messages are
not as clear as they could be.
Stephen Boyd (3):
lib/hexdump: Add a raw pointer printing format for slub debugging
slub: Print raw pointer addresses when debugging
slub: Actually use 'message' in restore_bytes()
include/linux/printk.h | 1 +
lib/hexdump.c | 12 ++++++++++--
mm/slub.c | 24 ++++++++++++------------
3 files changed, 23 insertions(+), 14 deletions(-)
base-commit: 6efb943b8616ec53a5e444193dccf1af9ad627b5
--
https://chromeos.dev
Powered by blists - more mailing lists