From: Ratheesh Kannoth <rkannoth@marvell.com>
To: David Ahern <dsahern@kernel.org>
Cc: <stephen@networkplumber.org>, <kuba@kernel.org>,
<linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
<andrew+netdev@lunn.ch>, <edumazet@google.com>,
<pabeni@redhat.com>, <jiri@resnulli.us>
Subject: Re: [PATCH iproute2-next v2 2/2] devlink: support u64-array values in devlink param show/set
Date: Wed, 1 Jul 2026 07:59:23 +0530 [thread overview]
Message-ID: <akR7g8aWfws3h2jx@rkannoth-OptiPlex-7090> (raw)
In-Reply-To: <9d9cceae-3934-4dd6-ae8e-af995ae6b0ab@kernel.org>
On 2026-06-30 at 20:06:17, David Ahern (dsahern@kernel.org) wrote:
> On 6/29/26 7:50 PM, Ratheesh Kannoth wrote:
> > diff --git a/devlink/devlink.c b/devlink/devlink.c
> > index 9372e92f..3c29601d 100644
> > --- a/devlink/devlink.c
> > +++ b/devlink/devlink.c
> > @@ -3496,13 +3496,115 @@ static const struct param_val_conv param_val_conv[] = {
> > };
> >
> > #define PARAM_VAL_CONV_LEN ARRAY_SIZE(param_val_conv)
> > +#define DEVLINK_PARAM_MAX_ARRAY_SIZE 32
>
> Why 32? Is that based on current code?
Yes, this aligns with the current kernel-side limits. See:
https://lore.kernel.org/all/20260609040453.711932-5-rkannoth@marvell.com/
>How does the kernel side handle
> the number of parameters? What happens if the kernel sends more than 32
> parameters - from a user's perspective, not this code and processing the
> output?
The kernel strictly validates and restricts the number of parameters. To be safe, this patch
adds an explicit bounds check to prevent userspace issues if that threshold is ever crossed.
Ideally, since "union devlink_param_value" is omitted from the UAPI, we have to define
DEVLINK_PARAM_MAX_ARRAY_SIZE here. Moving the underlying structures to the UAPI in the
future would allow us to share a single definition and avoid this hardcoded value in userspace.
>
> > +
> > +struct devlink_param_u64_array {
> > + uint64_t size;
> > + uint64_t val[DEVLINK_PARAM_MAX_ARRAY_SIZE];
> > +};
> > +
> > +
> > +static int param_value_u64_array_put_from_str(struct nlmsghdr *nlh,
> > + const char *param_value,
> > + const struct devlink_param_u64_array *cur)
> > +{
> > + struct devlink_param_u64_array new_arr = {};
> > + char *copy, *token, *saveptr = NULL;
> > + char delim[] = " ,";
> > + uint64_t val;
> > + int err;
> > +
> > + copy = strdup(param_value);
> > + if (!copy)
> > + return -ENOMEM;
> > +
> > + token = strtok_r(copy, delim, &saveptr);
> > + while (token) {
> > + if (new_arr.size >= DEVLINK_PARAM_MAX_ARRAY_SIZE) {
> > + free(copy);
> > + pr_err("Too many array elements (max %d)\n",
> > + DEVLINK_PARAM_MAX_ARRAY_SIZE);
> > + return -EINVAL;
> > + }
> > + err = get_u64((__u64 *)&val, token, 10);
> > + if (err) {
> > + free(copy);
> > + pr_err("Value \"%s\" is not a number or not within range\n",
> > + token);
> > + return err;
> > + }
> > + new_arr.val[new_arr.size++] = val;
> > + token = strtok_r(NULL, delim, &saveptr);
> > + }
> > + free(copy);
> > +
> > + if (cur && param_value_u64_array_equal(&new_arr, cur))
> > + return 1;
> > +
> > + for (uint64_t i = 0; i < new_arr.size; i++)
>
> put the declaration at the top of the function with the rest of them.
> global comment; fix all of them.
ACK.
>
> > + mnl_attr_put_u64(nlh, DEVLINK_ATTR_PARAM_VALUE_DATA, new_arr.val[i]);
>
> Why can't this put be done in the loop above as the string is processed?
ACK.
>
next prev parent reply other threads:[~2026-07-01 2:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 1:50 [PATCH iproute2-next v2 0/2] devlink: support u64-array devlink parameters Ratheesh Kannoth
2026-06-30 1:50 ` [PATCH iproute2-next v2 1/2] devlink: use DEVLINK_VAR_ATTR_TYPE_* in param show/set Ratheesh Kannoth
2026-06-30 1:50 ` [PATCH iproute2-next v2 2/2] devlink: support u64-array values in devlink " Ratheesh Kannoth
2026-06-30 14:36 ` David Ahern
2026-07-01 2:29 ` Ratheesh Kannoth [this message]
2026-07-01 14:34 ` David Ahern
2026-07-01 2:57 ` Ratheesh Kannoth
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=akR7g8aWfws3h2jx@rkannoth-OptiPlex-7090 \
--to=rkannoth@marvell.com \
--cc=andrew+netdev@lunn.ch \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stephen@networkplumber.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