From: Ido Schimmel <idosch@idosch.org>
To: Bernard Zhao <bernard@vivo.com>
Cc: Roopa Prabhu <roopa@nvidia.com>,
Nikolay Aleksandrov <nikolay@nvidia.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
bridge@lists.linux-foundation.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net/bridge: replace simple_strtoul to kstrtol
Date: Mon, 22 Nov 2021 12:04:35 +0200 [thread overview]
Message-ID: <YZtrM3Ukz7rKfNLN@shredder> (raw)
In-Reply-To: <20211119020642.108397-1-bernard@vivo.com>
On Thu, Nov 18, 2021 at 06:06:42PM -0800, Bernard Zhao wrote:
> simple_strtoull is obsolete, use kstrtol instead.
>
> Signed-off-by: Bernard Zhao <bernard@vivo.com>
> ---
> net/bridge/br_sysfs_br.c | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/net/bridge/br_sysfs_br.c b/net/bridge/br_sysfs_br.c
> index d9a89ddd0331..11c490694296 100644
> --- a/net/bridge/br_sysfs_br.c
> +++ b/net/bridge/br_sysfs_br.c
> @@ -36,15 +36,14 @@ static ssize_t store_bridge_parm(struct device *d,
> struct net_bridge *br = to_bridge(d);
> struct netlink_ext_ack extack = {0};
> unsigned long val;
> - char *endp;
> int err;
>
> if (!ns_capable(dev_net(br->dev)->user_ns, CAP_NET_ADMIN))
> return -EPERM;
>
> - val = simple_strtoul(buf, &endp, 0);
> - if (endp == buf)
> - return -EINVAL;
> + err = kstrtoul(buf, 10, &val);
Base 16 is valid.
Before this patch:
# ip link add name br0 type bridge vlan_filtering 1
# echo "0x88a8" > /sys/class/net/br0/bridge/vlan_protocol
# echo $?
0
After this patch:
# ip link add name br0 type bridge vlan_filtering 1
# echo "0x88a8" > /sys/class/net/br0/bridge/vlan_protocol
bash: echo: write error: Invalid argument
> + if (err != 0)
> + return err;
>
> if (!rtnl_trylock())
> return restart_syscall();
> --
> 2.33.1
>
next prev parent reply other threads:[~2021-11-22 10:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-19 2:06 [PATCH] net/bridge: replace simple_strtoul to kstrtol Bernard Zhao
2021-11-19 14:20 ` patchwork-bot+netdevbpf
2021-11-20 21:57 ` David Laight
2021-11-22 10:04 ` Ido Schimmel [this message]
2021-11-22 10:17 ` Nikolay Aleksandrov
2021-11-24 4:13 ` Jakub Kicinski
2021-11-24 10:18 ` Nikolay Aleksandrov
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=YZtrM3Ukz7rKfNLN@shredder \
--to=idosch@idosch.org \
--cc=bernard@vivo.com \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@nvidia.com \
--cc=roopa@nvidia.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