From: Thomas Monjalon <thomas@monjalon.net>
To: Anatoly Burakov <anatoly.burakov@intel.com>
Cc: dev@dpdk.org, janos.kobor@ericsson.com,
marton.a.toth@ericsson.com, laszlo.madarassy@ericsson.com
Subject: Re: [dpdk-dev] [PATCH] malloc: fix invalid argument handling
Date: Mon, 05 Nov 2018 23:21:32 +0100 [thread overview]
Message-ID: <2807317.8dekEOir4J@xps> (raw)
In-Reply-To: <35c09f98cfc044d9030c96bd6021d4b2e8246a45.1541438600.git.anatoly.burakov@intel.com>
05/11/2018 18:26, Anatoly Burakov:
> When adding memory to an external heap, do not go to unlock failure
> handler because the memory hotplug lock hasn't been taken out yet.
>
> Fixes: 7d75c31014f7 ("malloc: allow adding memory to named heaps")
>
> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
Applied, thanks
prev parent reply other threads:[~2018-11-05 22:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 17:26 Anatoly Burakov
2018-11-05 22:21 ` 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=2807317.8dekEOir4J@xps \
--to=thomas@monjalon.net \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=janos.kobor@ericsson.com \
--cc=laszlo.madarassy@ericsson.com \
--cc=marton.a.toth@ericsson.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).