mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Laight <david.laight.linux@gmail.com>
To: iamzayn19 <iamzayn19@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scripts: bloat-o-meter: avoid shell for nm invocation
Date: Sun, 27 Sep 2026 08:13:22 +0100	[thread overview]
Message-ID: <20260927081322.26a44ce0@pumpkin> (raw)
In-Reply-To: <20260927053441.86594-1-iamzayn19@gmail.com>

On Sun, 27 Sep 2026 10:34:41 +0500
iamzayn19 <iamzayn19@gmail.com> wrote:

> bloat-o-meter builds the nm command with string formatting and then
> executes it through the shell. Object file paths containing spaces are
> split before nm sees them, so the comparison silently reports empty
> results for those files.

Where are pathnames with spaces coming from?
Make doesn't support them.
Even some windows build environments don't support them.

David

> 
> Invoke nm with subprocess argv instead. This preserves paths as single
> arguments and avoids shell interpretation of filenames and tool prefixes.
> 
> Assisted-by: LLM
> Signed-off-by: iamzayn19 <iamzayn19@gmail.com>
> ---
>  scripts/bloat-o-meter | 10 +++++++---
>  1 file changed, 7 insertions(+), 3 deletions(-)
> 
> diff --git a/scripts/bloat-o-meter b/scripts/bloat-o-meter
> index 5868a8b..72edbb7 100755
> --- a/scripts/bloat-o-meter
> +++ b/scripts/bloat-o-meter
> @@ -7,7 +7,7 @@
>  # This software may be used and distributed according to the terms
>  # of the GNU General Public License, incorporated herein by reference.
>  
> -import sys, os, re, argparse
> +import argparse, re, subprocess
>  from signal import signal, SIGPIPE, SIG_DFL
>  
>  signal(SIGPIPE, SIG_DFL)
> @@ -31,8 +31,11 @@ def getsizes(file, format):
>      if args.prefix:
>          nm = "{}nm".format(args.prefix)
>  
> -    with os.popen("{} --size-sort {}".format(nm, file)) as f:
> -        for line in f:
> +    with subprocess.Popen([nm, "--size-sort", file], stdout=subprocess.PIPE,
> +                          text=True) as f:
> +        if f.stdout is None:
> +            return sym
> +        for line in f.stdout:
>              if line.startswith("\n") or ":" in line:
>                  continue
>              size, type, name = line.split()
> @@ -49,6 +52,7 @@ def getsizes(file, format):
>                  # statics and some other optimizations adds random .NUMBER
>                  name = re_NUMBER.sub('', name)
>                  sym[name] = sym.get(name, 0) + int(size, 16)
> +        f.wait()
>      return sym
>  
>  def calc(oldfile, newfile, format):


      reply	other threads:[~2026-09-27  7:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-27  5:34 iamzayn19
2026-09-27  7:13 ` David Laight [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=20260927081322.26a44ce0@pumpkin \
    --to=david.laight.linux@gmail.com \
    --cc=iamzayn19@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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®