From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Tyler Retzlaff <roretzla@linux.microsoft.com>,
Chengwen Feng <fengchengwen@huawei.com>,
Anatoly Burakov <anatoly.burakov@intel.com>
Subject: Re: [PATCH v4] doc/eal: add signal safety warning
Date: Wed, 9 Nov 2022 15:17:06 -0800 [thread overview]
Message-ID: <20221109151706.0af510d5@hermes.local> (raw)
In-Reply-To: <20220711230448.557715-1-stephen@networkplumber.org>
On Mon, 11 Jul 2022 16:04:48 -0700
Stephen Hemminger <stephen@networkplumber.org> wrote:
> The DPDK is not designed to be used from a signal handler.
> Add a notice in the documentation describing this limitation,
> similar to Linux signal-safety manual page.
>
> Bugzilla ID: 1030
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> Acked-by: Tyler Retzlaff <roretzla@linux.microsoft.com>
> Acked-by: Chengwen Feng <fengchengwen@huawei.com>
There have been reports of this problem, multiple ack's of this patch
but it is still not merged. It documents a real problem that will trap
users.
next prev parent reply other threads:[~2022-11-09 23:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 15:23 [PATCH] doc/eal: add signal safety warning Stephen Hemminger
2022-06-10 22:53 ` Tyler Retzlaff
2022-06-10 23:38 ` Stephen Hemminger
2022-06-10 23:42 ` Tyler Retzlaff
2022-06-11 1:37 ` fengchengwen
2022-06-11 16:50 ` Mattias Rönnblom
2022-07-05 20:44 ` [PATCH v2] " Stephen Hemminger
2022-07-11 21:15 ` Thomas Monjalon
2022-07-11 21:31 ` Stephen Hemminger
2022-10-21 19:58 ` Stephen Hemminger
2022-07-11 23:02 ` [PATCH v3] " Stephen Hemminger
2022-07-11 23:04 ` [PATCH v4] " Stephen Hemminger
2022-11-09 23:17 ` Stephen Hemminger [this message]
2022-11-15 16:21 ` David Marchand
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=20221109151706.0af510d5@hermes.local \
--to=stephen@networkplumber.org \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=roretzla@linux.microsoft.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 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.