From: Kevin Traynor <ktraynor@redhat.com>
To: Fengnan Chang <changfengnan@bytedance.com>
Cc: dpdk stable <stable@dpdk.org>
Subject: Re: [PATCH 21.11] eal: cleanup alarm and hotplug before memory detach
Date: Mon, 20 Mar 2023 16:20:08 +0000 [thread overview]
Message-ID: <a39e3852-b9d9-1169-067a-d961218f70b6@redhat.com> (raw)
In-Reply-To: <20230316114818.99552-1-changfengnan@bytedance.com>
On 16/03/2023 11:48, Fengnan Chang wrote:
> Alarm and multiprocess hotplug still need access hugepage memory,
> if alarm event processed after memory detach, it may cause SEGV.
> So cleanup alarm and multiprocess hotplug before memory detach.
>
> Signed-off-by: Fengnan Chang <changfengnan@bytedance.com>
> ---
> lib/eal/freebsd/eal.c | 2 +-
> lib/eal/linux/eal.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
Thanks Fengnan, added upstream commit id and pushed to 21.11 branch.
fyi for future, please note that explicit "backport only" patches go to
stable@dpdk.org mailing list and not dev@dpdk.org. Otherwise it might
get missed because of hitting the wrong email filter etc. though you did
Cc me which was a good idea :-)
Kevin
next parent reply other threads:[~2023-03-20 16:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230316114818.99552-1-changfengnan@bytedance.com>
2023-03-20 16:20 ` Kevin Traynor [this message]
2023-03-22 2:21 ` [External] " Fengnan Chang
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=a39e3852-b9d9-1169-067a-d961218f70b6@redhat.com \
--to=ktraynor@redhat.com \
--cc=changfengnan@bytedance.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 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).