From: Eric Wong <e@80x24.org>
To: cmogstored-public@bogomips.org
Subject: [PATCH 0/2] vfork safety fixes
Date: Wed, 1 Jun 2016 08:27:55 +0000 [thread overview]
Message-ID: <20160601082755.GA23982@dcvr.yhbt.net> (raw)
I doubt these affect any current use cases and I haven't heard
any reports, but better safe than sorry. Hopefully this makes
things easier for anybody who wants to audit the code (please
do so!).
Eric Wong (2):
stdin is always redirected to /dev/null
minor vfork/fork safety fixes
cloexec_from.c | 4 +--
cmogstored.c | 23 +++++++------
iostat_process.c | 100 +++++++++++++++++++++++++++++++++----------------------
process.c | 14 ++++++--
svc.c | 6 ++--
util.h | 2 +-
6 files changed, 91 insertions(+), 58 deletions(-)
next reply other threads:[~2016-06-01 8:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 8:27 Eric Wong [this message]
2016-06-01 8:28 ` [PATCH 1/2] stdin is always redirected to /dev/null Eric Wong
2016-06-01 8:28 ` [PATCH 2/2] minor vfork/fork safety fixes Eric Wong
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
List information: https://yhbt.net/cmogstored/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160601082755.GA23982@dcvr.yhbt.net \
--to=e@80x24.org \
--cc=cmogstored-public@bogomips.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.
Code repositories for project(s) associated with this public inbox
https://yhbt.net/cmogstored.git/
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 read-only IMAP folder(s) and NNTP newsgroup(s).