From: Jakub Kicinski <kuba@kernel.org>
To: Daehyeon Ko <4ncienth@gmail.com>
Cc: horms@kernel.org, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, netdev@vger.kernel.org
Subject: Re: [PATCH net] net: pktgen: reject out-of-range node indices
Date: Tue, 29 Sep 2026 18:52:31 -0700 [thread overview]
Message-ID: <20260929185231.297fe610@kernel.org> (raw)
In-Reply-To: <179059386581.3965069.15320036220559790742.pktgen-node-review@gmail.com>
On Mon, 28 Sep 2026 20:21:04 +0900 Daehyeon Ko wrote:
> I propose keeping the existing ten-digit decimal lexer and using
> kstrtoint(..., 10, ...) for conversion, retaining the existing ERROR
> result and write count. This removes the duplicate accumulator and
> prevents 32-bit wrap. A host comparison against the pinned parsers
> passed; this alternative has not yet been built or run as a kernel
> patch.
👍️
prev parent reply other threads:[~2026-09-30 1:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 5:37 [PATCH net] net: pktgen: reject out-of-range node indices Daehyeon Ko
2026-09-28 9:32 ` Simon Horman
2026-09-28 11:21 ` Daehyeon Ko
2026-09-30 1:52 ` Jakub Kicinski [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=20260929185231.297fe610@kernel.org \
--to=kuba@kernel.org \
--cc=4ncienth@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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