From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1194] l3fwd-cat: calling unsafe functions from signal handler
Date: Mon, 20 Mar 2023 17:08:20 +0000 [thread overview]
Message-ID: <bug-1194-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 998 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1194
Bug ID: 1194
Summary: l3fwd-cat: calling unsafe functions from signal
handler
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: examples
Assignee: dev@dpdk.org
Reporter: stephen@networkplumber.org
Target Milestone: ---
The handling of SIGINT and SIGTERM in the l2fwd-cat example is unsafe and
non-portable. The signal handler could be called by any thread at any time.
The current method (copy/paste from testpmd?) is to call cat_exit() in the
signal handler. This may race with other threads and cause problems.
The better solution is to set a flag in signal handler and then do the shutdown
aft er the main loop exits.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 2860 bytes --]
reply other threads:[~2023-03-20 17:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-1194-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@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).