From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Ilya Maximets <i.maximets@samsung.com>, dev@dpdk.org
Cc: solal.pirelli@gmail.com, stable@dpdk.org
Subject: Re: [PATCH v2] mem: fix undefined behavior in NUMA code
Date: Fri, 21 Sep 2018 09:57:02 +0100 [thread overview]
Message-ID: <5e5d7251-8d51-e413-ae49-cbaae562fa19@intel.com> (raw)
In-Reply-To: <20180921064524eucas1p147ff66419605b9b141969e1a672196f9~WV1A0hUgX1031210312eucas1p1k@eucas1p1.samsung.com>
On 21-Sep-18 7:47 AM, Ilya Maximets wrote:
> On 20.09.2018 15:50, Anatoly Burakov wrote:
>> When NUMA-aware hugepages config option is set, we rely on
>> libnuma to tell the kernel to allocate hugepages on a specific
>> NUMA node. However, we allocate node mask before we check if
>> NUMA is available in the first place, which, according to
>> the manpage [1], causes undefined behaviour.
>>
>> Fix by only using nodemask when we have NUMA available.
>>
>> [1] https://linux.die.net/man/3/numa_alloc_onnode
>>
>> Bugzilla ID: 20
>>
>> Fixes: 1b72605d2416 ("mem: balanced allocation of hugepages")
>> Cc: i.maximets@samsung.com
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
>> ---
>> lib/librte_eal/linuxapp/eal/eal_memory.c | 5 +++--
>> 1 file changed, 3 insertions(+), 2 deletions(-)
>>
>> diff --git a/lib/librte_eal/linuxapp/eal/eal_memory.c b/lib/librte_eal/linuxapp/eal/eal_memory.c
>> index dbf19499e..1a2a84a65 100644
>> --- a/lib/librte_eal/linuxapp/eal/eal_memory.c
>> +++ b/lib/librte_eal/linuxapp/eal/eal_memory.c
>> @@ -263,7 +263,7 @@ map_all_hugepages(struct hugepage_file *hugepg_tbl, struct hugepage_info *hpi,
>> int node_id = -1;
>> int essential_prev = 0;
>> int oldpolicy;
>> - struct bitmask *oldmask = numa_allocate_nodemask();
>> + struct bitmask *oldmask = NULL;
>> bool have_numa = true;
>> unsigned long maxnode = 0;
>>
>> @@ -275,6 +275,7 @@ map_all_hugepages(struct hugepage_file *hugepg_tbl, struct hugepage_info *hpi,
>>
>> if (have_numa) {
>> RTE_LOG(DEBUG, EAL, "Trying to obtain current memory policy.\n");
>> + oldmask = numa_allocate_nodemask();
>> if (get_mempolicy(&oldpolicy, oldmask->maskp,
>> oldmask->size + 1, 0, 0) < 0) {
>> RTE_LOG(ERR, EAL,
>> @@ -401,8 +402,8 @@ map_all_hugepages(struct hugepage_file *hugepg_tbl, struct hugepage_info *hpi,
>> strerror(errno));
>> numa_set_localalloc();
>> }
>> + numa_free_cpumask(oldmask);
>> }
>> - numa_free_cpumask(oldmask);
>
> There will be 'oldmask' leak in case no 'socket-mem' requested.
Oh, right, you're correct!
>
>> #endif
>> return i;
>> }
>>
>
--
Thanks,
Anatoly
next prev parent reply other threads:[~2018-09-21 8:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180829122139epcas1p13ad45026365d788c072f2ed7a38349fb@epcas1p1.samsung.com>
2018-08-29 12:21 ` [PATCH] mem: fix undefined behavior in NUMA code Anatoly Burakov
2018-08-29 13:02 ` Ilya Maximets
2018-09-20 12:50 ` [PATCH v2] " Anatoly Burakov
2018-09-21 6:47 ` Ilya Maximets
2018-09-21 8:57 ` Burakov, Anatoly [this message]
2018-09-21 9:27 ` [PATCH v3] " Anatoly Burakov
2018-09-21 11:02 ` Ilya Maximets
2018-10-03 22:36 ` [dpdk-stable] " Thomas Monjalon
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=5e5d7251-8d51-e413-ae49-cbaae562fa19@intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=i.maximets@samsung.com \
--cc=solal.pirelli@gmail.com \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.