From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Emmanuel Roullit <emmanuel.roullit@gmail.com>
Cc: dev@dpdk.org, "Gonzalez Monroy,
Sergio" <sergio.gonzalez.monroy@intel.com>
Subject: Re: [dpdk-dev] [PATCH] eal: fail eal when no hugepages were found
Date: Sun, 29 Jan 2017 23:08:19 +0100 [thread overview]
Message-ID: <114310386.7azNsuM9Yc@xps13> (raw)
In-Reply-To: <20170124202202.31045-1-emmanuel.roullit@gmail.com>
2017-01-24 21:22, Emmanuel Roullit:
> Found with clang static analysis:
> lib/librte_eal/linuxapp/eal/eal_memory.c:1004:11:
> warning: Call to 'malloc' has an allocation size of 0 bytes
> tmp_hp = malloc(nr_hugepages * sizeof(struct hugepage_file));
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> The --no-huge case, where nr_hugepages would be 0
> as well, is handled earlier.
>
> Fixes: 5e823a451261 ("ethdev: remove some VF functions")
This commit reference seems wrong. Please check
prev parent reply other threads:[~2017-01-29 22:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 20:22 Emmanuel Roullit
2017-01-29 22:08 ` Thomas Monjalon [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=114310386.7azNsuM9Yc@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=emmanuel.roullit@gmail.com \
--cc=sergio.gonzalez.monroy@intel.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;
as well as URLs for NNTP newsgroup(s).