From: "Xu, HuilongX" <huilongx.xu@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "Xu, HuilongX" <huilongx.xu@intel.com>
Subject: [dpdk-dev] about memzone name size issue
Date: Tue, 31 May 2016 09:07:40 +0000 [thread overview]
Message-ID: <DF2A19295B96364286FEB7F3DDA27A4637B57022@SHSMSX101.ccr.corp.intel.com> (raw)
Hi all,
I find a issue on link_bonding unit test case.
When I run model6 test case, will generate core dump error.
I debug it, find the error code in function:
rte_mempool_create_empty(const char *name, unsigned n, unsigned elt_size,
unsigned cache_size, unsigned private_data_size,
int socket_id, unsigned flags)
{
.......................
ret = snprintf(mz_name, sizeof(mz_name), RTE_MEMPOOL_MZ_FORMAT, name);
if (ret < 0 || ret >= (int)sizeof(mz_name)) {
rte_errno = ENAMETOOLONG;
goto exit_unlock;
}
.........................
}
The memzone name size only 32 bytes, but the mz_name in link_bonding is bigger 32 bytes. Could we set memzone name size to 64 bytes ?
Thanks a lot
next reply other threads:[~2016-05-31 9:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 9:07 Xu, HuilongX [this message]
2016-05-31 13:17 Wiles, Keith
2016-05-31 13:58 ` Iremonger, Bernard
2016-06-01 0:34 ` Xu, HuilongX
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=DF2A19295B96364286FEB7F3DDA27A4637B57022@SHSMSX101.ccr.corp.intel.com \
--to=huilongx.xu@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).