Base: WritePlatformFile now retries the operation if

base/platform_file_posix.cc

Index: base/platform_file_posix.cc
===================================================================
--- base/platform_file_posix.cc	(revision 97736)
+++ base/platform_file_posix.cc	(working copy)
@@ -155,10 +155,22 @@
 
 int WritePlatformFile(PlatformFile file, int64 offset,
                       const char* data, int size) {
-  if (file < 0)
+  if (file < 0 || size < 0)
     return -1;
 
-  return HANDLE_EINTR(pwrite(file, data, size, offset));
+  int bytes_written = 0;
+  int rv = -1;
+  while (bytes_written < size) {
+    rv = HANDLE_EINTR(pwrite(file, data + bytes_written,
+                             size - bytes_written, offset + bytes_written));
+
+    if (rv <= 0)
+      break;
+
+    bytes_written += rv;
+  }
+
+  return bytes_written ? bytes_written : (size ? rv : 0);

[Scott Hess - ex-Googler, 2011/08/25 21:05:23]

If !bytes_written && !size, then rv<=0, so I think you don't need the latter
conditional operator.

[rvargas (doing something else), 2011/08/25 21:28:06]

I want to return 0 instead of -1 (rv) if !size, and at the same time return the
same error that pwrite returns if there is a failure (not force a -1)

[Scott Hess - ex-Googler, 2011/08/25 21:33:01]

This means that the code changes to always return 0 for size==0, whereas before
it would only return 0 for size==0 if the 0-sized write was successful.  This
might matter if, for instance, someone is testing if the file is writable, but
not writing anything to it.  They should be repremanded, though.

Actually, I just noticed that the current code doesn't even call pwrite() when
size==0.  If this is the right thing to do, you could just handle it before the
loop.

[rvargas (doing something else), 2011/08/25 21:37:50]

No, that's not what I meant... fixing it.

 }
 
 bool TruncatePlatformFile(PlatformFile file, int64 length) {