From: David Laight <david.laight.linux@gmail.com>
To: Doug Anderson <dianders@chromium.org>
Cc: Naveen Kumar Chaudhary <naveen.osdev@gmail.com>,
jason.wessel@windriver.com, danielt@kernel.org,
kgdb-bugreport@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] kdb: unify CMD_BUFLEN definition into kdb_private.h
Date: Thu, 18 Jun 2026 21:56:42 +0100 [thread overview]
Message-ID: <20260618215642.186c65b4@pumpkin> (raw)
In-Reply-To: <CAD=FV=VsbhjtVMOh9h=MUrnm6MJzzoGhV4jKcrc=x_oWes3KPg@mail.gmail.com>
On Thu, 18 Jun 2026 09:02:38 -0700
Doug Anderson <dianders@chromium.org> wrote:
....
> We've had several rounds of patches improving string safety. If you
> can show any missed cases, please send a patch. In this day and age,
> if there are problems, it's probably a matter of time before AI sends
> us patches. I presume Naveen ended up here to begin with because AI
> pointed out the problems that he's fixing.
One set is mine :-)
Trying to get in some patches that actually check things properly
rather than blind substitutions.
Clearly some changes are to code that is actually safe - but only
with a deeper analysis than compiler checks can do.
-- David
>
> -Doug
next prev parent reply other threads:[~2026-06-18 20:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-16 16:44 [PATCH] kdb: use sizeof(kdb_prompt_str) instead of mismatched CMD_BUFLEN Naveen Kumar Chaudhary
2026-06-16 20:20 ` David Laight
2026-06-16 22:06 ` Doug Anderson
2026-06-16 22:04 ` Doug Anderson
2026-06-17 2:28 ` [PATCH v2] kdb: unify CMD_BUFLEN definition into kdb_private.h Naveen Kumar Chaudhary
2026-06-17 3:00 ` Naveen Kumar Chaudhary
2026-06-17 21:16 ` Doug Anderson
2026-06-18 10:04 ` David Laight
2026-06-18 16:02 ` Doug Anderson
2026-06-18 20:56 ` David Laight [this message]
2026-06-25 12:52 ` Daniel Thompson
2026-06-17 10:43 ` [PATCH] kdb: use sizeof(kdb_prompt_str) instead of mismatched CMD_BUFLEN kernel test robot
2026-06-17 19:49 ` kernel test robot
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=20260618215642.186c65b4@pumpkin \
--to=david.laight.linux@gmail.com \
--cc=danielt@kernel.org \
--cc=dianders@chromium.org \
--cc=jason.wessel@windriver.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=naveen.osdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox