From: "Simon Kågström" <simon.kagstrom@netinsight.net>
To: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Unsafe array accesses in rte_sched.c
Date: Fri, 16 Oct 2015 15:50:55 +0200 [thread overview]
Message-ID: <562100BF.9010107@netinsight.net> (raw)
In-Reply-To: <3EB4FA525960D640B5BDFFD6A3D89126478F0C50@IRSMSX108.ger.corp.intel.com>
On 2015-10-16 15:39, Dumitrescu, Cristian wrote:
>> port->qsize_add[12] = port->qsize_add[11] + port->qsize[2];
>> port->qsize_add[13] = port->qsize_add[12] + port->qsize[3];
>> port->qsize_add[14] = port->qsize_add[13] + port->qsize[3];
>> port->qsize_add[15] = port->qsize_add[14] + port->qsize[3];
>>
>> port->qsize_sum = port->qsize_add[15] + port->qsize[3];
>> }
>>
>> but port->qsize is actually defined as
>>
>> uint16_t qsize[RTE_SCHED_TRAFFIC_CLASSES_PER_PIPE];
>>
>
> Not sure what you see "unsafe" here: qsize is an array of 4 elements, while qsize_add is a different array of 16 elements? Please explain.
Sorry, I should have been more explicit: What I mean that the code
should loop over RTE_SCHED_TRAFFIC_CLASSES_PER_PIPE instead of
hard-coding the numbers.
It certainly works with the current RTE_SCHED_TRAFFIC_CLASSES_PER_PIPE,
but it would be safer (and in my opinion more clear) if it would not
assume RTE_SCHED_TRAFFIC_CLASSES_PER_PIPE == 4.
// Simon
next prev parent reply other threads:[~2015-10-16 13:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 8:49 Simon Kågström
2015-10-16 13:39 ` Dumitrescu, Cristian
2015-10-16 13:50 ` Simon Kågström [this message]
2015-10-16 16:10 ` Stephen Hemminger
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=562100BF.9010107@netinsight.net \
--to=simon.kagstrom@netinsight.net \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.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;
as well as URLs for NNTP newsgroup(s).