From: Alasdair G Kergon <agk@redhat.com>
To: lvm-devel@redhat.com
Subject: [PATCH] dmeventd -R (restart; BZ 454618)
Date: Wed, 6 Oct 2010 00:49:45 +0100 [thread overview]
Message-ID: <20101005234945.GG1200@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <BCC2498C-1B82-4462-A9FE-27823E22DEA2@redhat.com>
>> + kill(pid, 9);
I'm paranoid about code like that, and want to see everything reasonably
possible done to ensure it can only kill the process it should and
any possible races are clearly documented and defended against.
Alasdair
next prev parent reply other threads:[~2010-10-05 23:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 10:45 [PATCH] dmeventd -R (restart; BZ 454618) Petr Rockai
2010-10-05 12:54 ` ejt
2010-10-12 16:05 ` Petr Rockai
2010-10-05 21:31 ` Jonathan Brassow
2010-10-05 23:49 ` Alasdair G Kergon [this message]
2010-10-06 14:07 ` Petr Rockai
2010-10-19 14:51 ` Zdenek Kabelac
2010-10-19 15:00 ` Alasdair G Kergon
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=20101005234945.GG1200@agk-dp.fab.redhat.com \
--to=agk@redhat.com \
--cc=lvm-devel@redhat.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.