From: "M. Mohan Kumar" <mohan@in.ibm.com>
To: qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@gmail.com>
Subject: [Qemu-devel] [V10 PATCH 01/13] Implement qemu_read_full
Date: Thu, 31 Mar 2011 13:51:28 +0530 [thread overview]
Message-ID: <1301559700-6742-2-git-send-email-mohan@in.ibm.com> (raw)
In-Reply-To: <1301559700-6742-1-git-send-email-mohan@in.ibm.com>
Add qemu_read_full function
Signed-off-by: M. Mohan Kumar <mohan@in.ibm.com>
---
osdep.c | 32 ++++++++++++++++++++++++++++++++
qemu-common.h | 2 ++
2 files changed, 34 insertions(+), 0 deletions(-)
diff --git a/osdep.c b/osdep.c
index 327583b..8d84a88 100644
--- a/osdep.c
+++ b/osdep.c
@@ -127,6 +127,38 @@ ssize_t qemu_write_full(int fd, const void *buf, size_t count)
}
/*
+ * A variant of read(2) which handles interrupted read.
+ * Simlar to qemu_write_full function
+ *
+ * Return the number of bytes read.
+ *
+ * This function does not work with non-blocking fd's.
+ * errno is set if fewer than `count' bytes are read because of any
+ * error
+ */
+ssize_t qemu_read_full(int fd, void *buf, size_t count)
+{
+ ssize_t ret = 0;
+ ssize_t total = 0;
+
+ while (count) {
+ ret = read(fd, buf, count);
+ if (ret <= 0) {
+ if (errno == EINTR) {
+ continue;
+ }
+ break;
+ }
+
+ count -= ret;
+ buf += ret;
+ total += ret;
+ }
+
+ return total;
+}
+
+/*
* Opens a socket with FD_CLOEXEC set
*/
int qemu_socket(int domain, int type, int protocol)
diff --git a/qemu-common.h b/qemu-common.h
index 40dad52..325b16a 100644
--- a/qemu-common.h
+++ b/qemu-common.h
@@ -207,6 +207,8 @@ void qemu_mutex_unlock_iothread(void);
int qemu_open(const char *name, int flags, ...);
ssize_t qemu_write_full(int fd, const void *buf, size_t count)
QEMU_WARN_UNUSED_RESULT;
+ssize_t qemu_read_full(int fd, void *buf, size_t count)
+ QEMU_WARN_UNUSED_RESULT;
void qemu_set_cloexec(int fd);
#ifndef _WIN32
--
1.7.4
next prev parent reply other threads:[~2011-03-31 8:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 8:21 [Qemu-devel] [V10 PATCH 00/13] virtio-9p: Use chroot to safely access files in passthrough security model M. Mohan Kumar
2011-03-31 8:21 ` M. Mohan Kumar [this message]
2011-03-31 8:21 ` [Qemu-devel] [V10 PATCH 02/13] virtio-9p: Enable CONFIG_THREAD if CONFIG_VIRTFS is enabled M. Mohan Kumar
2011-03-31 8:21 ` [Qemu-devel] [V10 PATCH 03/13] virtio-9p: Provide chroot worker side interfaces M. Mohan Kumar
2011-03-31 8:21 ` [Qemu-devel] [V10 PATCH 04/13] virtio-9p: Add qemu side interfaces for chroot environment M. Mohan Kumar
2011-03-31 8:21 ` [Qemu-devel] [V10 PATCH 05/13] virtio-9p: Add support to open a file in " M. Mohan Kumar
2011-03-31 8:21 ` [Qemu-devel] [V10 PATCH 06/13] virtio-9p: Create support " M. Mohan Kumar
2011-03-31 8:21 ` [Qemu-devel] [V10 PATCH 07/13] virtio-9p: Support for creating special files M. Mohan Kumar
2011-03-31 8:21 ` [Qemu-devel] [V10 PATCH 08/13] virtio-9p: Add support for removing file or directory M. Mohan Kumar
2011-03-31 8:21 ` [Qemu-devel] [V10 PATCH 09/13] virtio-9p: Add support to rename M. Mohan Kumar
2011-03-31 8:21 ` [Qemu-devel] [V10 PATCH 10/13] virtio-9p: Move file post creation changes to none security model M. Mohan Kumar
2011-03-31 8:21 ` [Qemu-devel] [V10 PATCH 11/13] virtio-9p: Add support for chmod M. Mohan Kumar
2011-03-31 8:21 ` [Qemu-devel] [V10 PATCH 12/13] virtio-9p: Add support for chown M. Mohan Kumar
2011-03-31 8:21 ` [Qemu-devel] [V10 PATCH 13/13] virtio-9p: Chroot environment for other functions M. Mohan Kumar
2011-04-08 8:44 ` [Qemu-devel] Re: [V10 PATCH 00/13] virtio-9p: Use chroot to safely access files in passthrough security model Stefan Hajnoczi
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=1301559700-6742-2-git-send-email-mohan@in.ibm.com \
--to=mohan@in.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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 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).