From: Stephen Hemminger <stephen@networkplumber.org>
To: Prashanth Swaminathan <prashanthsw@google.com>
Cc: netdev@vger.kernel.org, dsahern@kernel.org, maze@google.com,
yuyanghuang@google.com
Subject: Re: [PATCH iproute2] ss: bound fscanf width when reading comm in user_ent_hash_build_task
Date: Tue, 20 Oct 2026 19:46:57 -0700 [thread overview]
Message-ID: <20261020194657.5578513d@phoenix.local> (raw)
In-Reply-To: <CAHdA9ByY3mTg6JnwaQ2ACKSvkKLCq7VZTf6ay9BfpdmmJ4=Mfg@mail.gmail.com>
On Tue, 20 Oct 2026 15:13:58 -0700
Prashanth Swaminathan <prashanthsw@google.com> wrote:
> No problem. I couldn't find any definitive source on the org's current
> thinking regarding whether these types of hardening changes, which don't
> actually cover a security vulnerability, are desirable, so I erred on the
> side of caution. Apologies for the thrash!
It did motivate me to replace fscanf there, there already is a helper
in lib/fs.c just needs some small changes.
prev parent reply other threads:[~2026-10-21 2:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 16:59 [PATCH iproute2] ss: bound fscanf width when reading comm in user_ent_hash_build_task Prashanth Swaminathan
2026-10-20 18:06 ` Stephen Hemminger
[not found] ` <CAHdA9ByY3mTg6JnwaQ2ACKSvkKLCq7VZTf6ay9BfpdmmJ4=Mfg@mail.gmail.com>
2026-10-21 2:46 ` Stephen Hemminger [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=20261020194657.5578513d@phoenix.local \
--to=stephen@networkplumber.org \
--cc=dsahern@kernel.org \
--cc=maze@google.com \
--cc=netdev@vger.kernel.org \
--cc=prashanthsw@google.com \
--cc=yuyanghuang@google.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.