From: Laszlo Ersek <lersek@redhat.com>
To: qemu-devel@nongnu.org, qemu-trivial@nongnu.org, armbru@redhat.com
Subject: [Qemu-devel] [PATCH v2] keep the PID file locked for the lifetime of the process
Date: Fri, 27 Jan 2012 14:34:05 +0100 [thread overview]
Message-ID: <1327671245-5231-1-git-send-email-lersek@redhat.com> (raw)
In-Reply-To: <m31uqluvwy.fsf@blackfin.pond.sub.org>
The lockf() call in qemu_create_pidfile() aims at ensuring mutual
exclusion. We shouldn't close the pidfile on success (as introduced by
commit 1bbd1592), because that drops the lock as well [1]:
"File locks shall be released on first close by the locking process
of any file descriptor for the file."
Coverity may complain again about the leaked file descriptor; let's
worry about that later.
v1->v2:
- add reference to 1bbd1592
- explain the intentional fd leak in the source
[1] http://pubs.opengroup.org/onlinepubs/9699919799/functions/lockf.html
Signed-off-by: Laszlo Ersek <lersek@redhat.com>
---
os-posix.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/os-posix.c b/os-posix.c
index 5c437ca..e3ed497 100644
--- a/os-posix.c
+++ b/os-posix.c
@@ -348,6 +348,6 @@ int qemu_create_pidfile(const char *filename)
return -1;
}
- close(fd);
+ /* keep pidfile open & locked forever */
return 0;
}
--
1.7.1
next prev parent reply other threads:[~2012-01-27 13:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 21:36 [Qemu-devel] [PATCH] keep the PID file locked for the lifetime of the process Laszlo Ersek
2012-01-27 6:36 ` [Qemu-devel] [Qemu-trivial] " Stefan Hajnoczi
2012-01-27 8:56 ` Laszlo Ersek
2012-01-27 10:26 ` Daniel P. Berrange
2012-01-27 13:17 ` [Qemu-devel] " Markus Armbruster
2012-01-27 13:34 ` Laszlo Ersek [this message]
2012-01-27 14:48 ` [Qemu-devel] [PATCH v2] " Markus Armbruster
2012-02-03 17:21 ` Anthony Liguori
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=1327671245-5231-1-git-send-email-lersek@redhat.com \
--to=lersek@redhat.com \
--cc=armbru@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.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).