From: "Lin Ma" <linma@zju.edu.cn>
To: "Victor Nogueira" <victor@mojatatu.com>
Cc: jhs@mojatatu.com, xiyou.wangcong@gmail.com, jiri@resnulli.us,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] net/sched: mqprio: Add length check for TCA_MQPRIO_{MAX/MIN}_RATE64
Date: Mon, 24 Jul 2023 09:19:14 +0800 (GMT+08:00) [thread overview]
Message-ID: <225079a8.e02fc.189857aa264.Coremail.linma@zju.edu.cn> (raw)
In-Reply-To: <fe7cba2c-a0da-b1bd-1f0b-c6ecfa10de81@mojatatu.com>
Hello Victor,
>
> Shouldn't the check be nla_len(attr) != sizeof(u64)?
> An attribute with a bigger length also seems to be invalid.
>
> You could also separate this check into another if statement,
> so that the error message is clearer in regards to why the attr is
> invalid. Something like:
>
> if (nla_len(attr) != sizeof(u64)) {
> NL_SET_ERR_MSG_ATTR_FMT(extack, attr,
> "Attribute length expected to be %lu",
> sizeof(u64));
> return -EINVAL;
> }
>
> > NL_SET_ERR_MSG_ATTR(extack, attr,
> > "Attribute type expected to be TCA_MQPRIO_MIN_RATE64");
> > return -EINVAL;
> > @@ -307,7 +308,8 @@ static int mqprio_parse_nlattr(struct Qdisc *sch, struct tc_mqprio_qopt *qopt,
> > i = 0;
> > nla_for_each_nested(attr, tb[TCA_MQPRIO_MAX_RATE64],
> > rem) {
> > - if (nla_type(attr) != TCA_MQPRIO_MAX_RATE64) {
> > + if (nla_type(attr) != TCA_MQPRIO_MAX_RATE64 ||
> > + nla_len(attr) < sizeof(u64)) {
>
> Same as the previous comment.
>
> > NL_SET_ERR_MSG_ATTR(extack, attr,
> > "Attribute type expected to be TCA_MQPRIO_MAX_RATE64");
> > return -EINVAL;
>
> cheers,
> Victor
Yeah, I use < instead of != for a looser check. I agree with you the "!=" condition and the separation suggestion.
I will prepare the v2 ASAP.
Thanks
Lin
prev parent reply other threads:[~2023-07-24 1:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-23 7:56 Lin Ma
2023-07-23 21:41 ` Victor Nogueira
2023-07-24 1:19 ` Lin Ma [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=225079a8.e02fc.189857aa264.Coremail.linma@zju.edu.cn \
--to=linma@zju.edu.cn \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jhs@mojatatu.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=victor@mojatatu.com \
--cc=xiyou.wangcong@gmail.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
all inboxes | Powered by JetHome®