All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Carlos Eduardo <otakurack@gmail.com>
Cc: luis.augenstein@tngtech.com, maximilian.huber@tngtech.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scripts/sbom: catch ValueError from malformed shell quoting
Date: Sun, 19 Jul 2026 09:42:47 +0200	[thread overview]
Message-ID: <2026071902-overfed-stunner-b086@gregkh> (raw)
In-Reply-To: <CAGf2LZe-8bRdsRJO2CzbTcOE5X9oDUDzYTRZQM+hLUH5gg8-mQ@mail.gmail.com>

On Sun, Jul 19, 2026 at 04:26:57AM -0300, Carlos Eduardo wrote:
> On Sun, Jul 19, 2026 at 02:24:17AM -0300, Greg KH wrote:
> > Do we have this today in the build system?
> 
> Sorry for my previous reply. I'm still learning the Linux kernel mailing
> list workflow.

This was sent in html format, which the lists reject :(

> The code path exists in the current implementation because the SBOM
> generator parses the .cmd files generated by Kbuild.
> 
> However, I have not observed malformed .cmd files produced by a normal
> kernel build. My intention with this patch was to make the parser behave
> consistently in tolerant mode (fail_on_unknown_build_command=False) when
> given malformed or corrupted inputs, rather than to fix an issue known to
> occur during standard kernel builds.

Ok, that's fine, just wanted to check if this is needed to fix a bug
today, but you are just making this more "robust".

And how did you find this bug?

Can you include that information in your changelog text and fix up the
authorship/signed-off-by information?

thanks,

greg k-h

  parent reply	other threads:[~2026-07-19  7:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-18 18:44 [PATCH] scripts/sbom: catch ValueError from malformed shell quoting kadu04t
2026-07-19  5:24 ` Greg KH
2026-07-19  5:24 ` Greg KH
2026-07-19  7:41   ` Carlos Sampaio Ribeiro
     [not found]   ` <CAGf2LZe-8bRdsRJO2CzbTcOE5X9oDUDzYTRZQM+hLUH5gg8-mQ@mail.gmail.com>
2026-07-19  7:42     ` Greg KH [this message]
2026-07-19  8:18       ` [PATCH v2] " Carlos Sampaio Ribeiro

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=2026071902-overfed-stunner-b086@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luis.augenstein@tngtech.com \
    --cc=maximilian.huber@tngtech.com \
    --cc=otakurack@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.