From: Eric-Terminal <ericterminal@gmail.com>
To: horms@kernel.org, davem@davemloft.net, kuba@kernel.org
Cc: netdev@vger.kernel.org, bridge@lists.linux.dev,
linux-nfs@vger.kernel.org, Yufan Chen <ericterminal@gmail.com>
Subject: [PATCH v3 0/2] net: replace deprecated simple_strto* parsers
Date: Tue, 24 Mar 2026 23:30:34 +0800 [thread overview]
Message-ID: <20260324153036.86901-1-ericterminal@gmail.com> (raw)
From: Yufan Chen <ericterminal@gmail.com>
Hi,
This series replaces deprecated simple_strto* parsers in two net paths
with kstrto* helpers and tightens parse semantics.
The series has been split from a previous mixed 9p/net series to ease
review and align with subsystem boundaries.
Patch 1 switches bridge brport_store() to kstrtoul() to ensure strict
input validation before taking locks.
Patch 2 updates sunrpc proc_dodebug() to use kstrtouint() for full-token
conversion, improving error reporting consistency in sysctl paths.
Testing:
- Verified migration to kstrto* ensures that sysfs/procfs interfaces now
properly validate the entire input string, rejecting malformed input.
v3:
- Split into a dedicated net series for bridge and sunrpc.
- No functional changes since v2.
Yufan Chen (2):
net: bridge: replace deprecated simple_strtoul with kstrtoul
net: sunrpc: replace deprecated simple_strtol with kstrtouint
net/bridge/br_sysfs_if.c | 5 +++--
net/sunrpc/sysctl.c | 24 ++++++++++++------------
2 files changed, 15 insertions(+), 14 deletions(-)
--
2.47.3
next reply other threads:[~2026-03-24 15:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 15:30 Eric-Terminal [this message]
2026-03-24 15:30 ` [PATCH v3 1/2] net: bridge: replace deprecated simple_strtoul with kstrtoul Eric-Terminal
2026-03-24 15:30 ` [PATCH v3 2/2] net: sunrpc: replace deprecated simple_strtol with kstrtouint Eric-Terminal
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=20260324153036.86901-1-ericterminal@gmail.com \
--to=ericterminal@gmail.com \
--cc=bridge@lists.linux.dev \
--cc=davem@davemloft.net \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=netdev@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