From: Vlastimil Babka <vbabka@suse.cz>
To: "Stéphane Graber" <stgraber@ubuntu.com>, linux-kernel@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Faiyaz Mohammed <faiyazm@codeaurora.org>,
stable@vger.kernel.org
Subject: Re: [PATCH] tools/vm/slabinfo: Handle files in debugfs
Date: Mon, 4 Apr 2022 15:40:44 +0200 [thread overview]
Message-ID: <29914f07-6ee5-a562-2b8e-ed15c861f3eb@suse.cz> (raw)
In-Reply-To: <20220331140339.1362390-1-stgraber@ubuntu.com>
On 3/31/22 16:03, Stéphane Graber wrote:
> Commit 64dd68497be76 relocated and renamed the alloc_calls and
> free_calls files from /sys/kernel/slab/NAME/*_calls over to
> /sys/kernel/debug/slab/NAME/*_calls but didn't update the slabinfo tool
> with the new location.
>
> This change will now have slabinfo look at the new location (and filenames)
> with a fallback to the prior files.
>
> Fixes: 64dd68497be76 ("mm: slub: move sysfs slab alloc/free interfaces to debugfs")
> Cc: stable@vger.kernel.org
> Signed-off-by: Stéphane Graber <stgraber@ubuntu.com>
> Tested-by: Stéphane Graber <stgraber@ubuntu.com>
> ---
> tools/vm/slabinfo.c | 26 ++++++++++++++++++++++++--
> 1 file changed, 24 insertions(+), 2 deletions(-)
>
> diff --git a/tools/vm/slabinfo.c b/tools/vm/slabinfo.c
> index 9b68658b6bb8..5b98f3ee58a5 100644
> --- a/tools/vm/slabinfo.c
> +++ b/tools/vm/slabinfo.c
> @@ -233,6 +233,24 @@ static unsigned long read_slab_obj(struct slabinfo *s, const char *name)
> return l;
> }
>
> +static unsigned long read_debug_slab_obj(struct slabinfo *s, const char *name)
> +{
> + char x[128];
> + FILE *f;
> + size_t l;
> +
> + snprintf(x, 128, "/sys/kernel/debug/slab/%s/%s", s->name, name);
> + f = fopen(x, "r");
> + if (!f) {
> + buffer[0] = 0;
> + l = 0;
> + } else {
> + l = fread(buffer, 1, sizeof(buffer), f);
> + buffer[l] = 0;
> + fclose(f);
> + }
> + return l;
> +}
slabinfo is not the nicest code already, but still this basically duplicates
read_slab_obj() just to add a prefix to the path, so it could be done in a
unified way?
>
> /*
> * Put a size string together
> @@ -409,14 +427,18 @@ static void show_tracking(struct slabinfo *s)
> {
> printf("\n%s: Kernel object allocation\n", s->name);
> printf("-----------------------------------------------------------------------\n");
> - if (read_slab_obj(s, "alloc_calls"))
> + if (read_debug_slab_obj(s, "alloc_traces"))
> + printf("%s", buffer);
> + else if (read_slab_obj(s, "alloc_calls"))
> printf("%s", buffer);
> else
> printf("No Data\n");
>
> printf("\n%s: Kernel object freeing\n", s->name);
> printf("------------------------------------------------------------------------\n");
> - if (read_slab_obj(s, "free_calls"))
> + if (read_debug_slab_obj(s, "free_traces"))
> + printf("%s", buffer);
> + else if (read_slab_obj(s, "free_calls"))
> printf("%s", buffer);
> else
> printf("No Data\n");
prev parent reply other threads:[~2022-04-04 13:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 14:03 Stéphane Graber
2022-04-04 13:40 ` Vlastimil Babka [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=29914f07-6ee5-a562-2b8e-ed15c861f3eb@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=faiyazm@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=stgraber@ubuntu.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®