@@ -12,6 +12,8 @@
ssize_t xread(int fd, void *buf, size_t count);
ssize_t xwrite(int fd, const void *buf, size_t count);
+ssize_t read_file(int fd, char *buf, size_t max_size);
+
ssize_t read_in_full(int fd, void *buf, size_t count);
ssize_t write_in_full(int fd, const void *buf, size_t count);
@@ -32,6 +32,27 @@ restart:
return nr;
}
+/*
+ * Read in the whole file while not exceeding max_size bytes of the buffer.
+ * Returns -1 (with errno set) in case of an error (ENOMEM if buffer was
+ * too small) or the filesize if the whole file could be read.
+ */
+ssize_t read_file(int fd, char *buf, size_t max_size)
+{
+ ssize_t ret;
+ char dummy;
+
+ errno = 0;
+ ret = read_in_full(fd, buf, max_size);
+
+ /* Probe whether we reached EOF. */
+ if (xread(fd, &dummy, 1) == 0)
+ return ret;
+
+ errno = ENOMEM;
+ return -1;
+}
+
ssize_t read_in_full(int fd, void *buf, size_t count)
{
ssize_t total = 0;
In various parts of kvmtool we simply try to read files into memory, but fail to do so in a safe way. The read(2) syscall can return early having only parts of the file read, or it may return -1 due to being interrupted by a signal (in which case we should simply retry). The ARM code seems to provide the only safe implementation, so take that as an inspiration to provide a generic read_file() function usable by every part of kvmtool. Signed-off-by: Andre Przywara <andre.przywara@arm.com> --- include/kvm/read-write.h | 2 ++ util/read-write.c | 21 +++++++++++++++++++++ 2 files changed, 23 insertions(+)