From: David Marchand <david.marchand@redhat.com>
To: Fengnan Chang <changfengnan@bytedance.com>
Cc: Thomas Monjalon <thomas@monjalon.net>, dev@dpdk.org
Subject: Re: [External] Re: [PATCH] eal: cleanup alarm and multiprocess hotplug before memory detach
Date: Tue, 13 Dec 2022 09:58:28 +0100 [thread overview]
Message-ID: <CAJFAV8xaaAk11rRqVVA17ihEMkzVZU2mGGpEBYTK7+guO1YAUg@mail.gmail.com> (raw)
In-Reply-To: <CAPFOzZsMLjz5K8=Z=opKt8gywem3058tKfY_0jd3YyYdaB533A@mail.gmail.com>
On Tue, Dec 13, 2022 at 9:54 AM Fengnan Chang
<changfengnan@bytedance.com> wrote:
>
> Thomas Monjalon <thomas@monjalon.net> 于2022年12月13日周二 16:34写道：
> >
> > 13/12/2022 08:59, Fengnan Chang:
> > > 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/linux/eal.c | 4 ++--
> > > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > What about FreeBSD?
> >
> FreeBSD may have same problem, I'll add FreeBSD in V2, before that I
> want wait a few days for more comments.
This fix is backport material, please add a Fixes: line.
Thanks.
--
David Marchand
next prev parent reply other threads:[~2022-12-13 8:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 7:59 Fengnan Chang
2022-12-13 8:34 ` Thomas Monjalon
2022-12-13 8:54 ` [External] " Fengnan Chang
2022-12-13 8:58 ` David Marchand [this message]
2023-02-09 12:03 ` [PATCH v2] " Fengnan Chang
2023-02-09 12:09 ` Fengnan Chang
2023-02-09 12:45 ` 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=CAJFAV8xaaAk11rRqVVA17ihEMkzVZU2mGGpEBYTK7+guO1YAUg@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=changfengnan@bytedance.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).