From: prateekag <prateekag@cse.iitb.ac.in>
To: dev@dpdk.org
Cc: thomas@monjalon.net
Subject: [dpdk-dev] Printfs in Signal Handler
Date: Tue, 01 Dec 2020 09:09:53 +0530 [thread overview]
Message-ID: <77fa0d526982e5fd0a15b293599d973c@cse.iitb.ac.in> (raw)
printf is not signal safe and may lead to deadlock if kept in signal handler
and
signal comes in two quick succession. It will not lead to incorrect behavior
and it is a highly unlikely event. And an expert may understand why this
issue happened. Is it worthwhile to change these printfs to unix I/O write
call?
Prateek Agarwal
next reply other threads:[~2020-12-02 14:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 3:39 prateekag [this message]
2020-12-01 9:24 ` Thomas Monjalon
2020-12-02 20:41 ` Thomas Monjalon
2020-12-03 0:02 ` prateekag
2020-12-04 9:20 ` prateekag
2020-12-04 9:50 ` Thomas Monjalon
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=77fa0d526982e5fd0a15b293599d973c@cse.iitb.ac.in \
--to=prateekag@cse.iitb.ac.in \
--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).