Fix bugs evidenced by change to keep flush errors on QFile::close

When closing a file, the contents of the write buffer should be emptied
even in the case where flush fails, so it doesn't leak to subsequent
files opened through the same instance. This is inline with what would
happen with native close on a buffered device.

Also changed the resource file engine to succeed on flush. Since all
writes fail there, logically it's write buffer is empty and flush should
succeed. This keeps auto-tests happy :-)

tst_QFile::fullDisk auto-test extended to ensure re-opening QFile does
not keep the write buffer alive.

Reviewed-by: Thiago Macieira

2 files changed, 4 insertions, 1 deletions

diff --git a/src/corelib/io/qfile.cpp b/src/corelib/io/qfile.cpp
index b6fa5f3..6395cc7 100644
--- a/src/corelib/io/qfile.cpp
+++ b/src/corelib/io/qfile.cpp
@@ -1389,6 +1389,9 @@ QFile::close()
     bool flushed = flush();
     QIODevice::close();
 
+    // reset write buffer
+    d->lastWasWrite = false;
+    d->writeBuffer.clear();
 
     // keep earlier error from flush
     if (fileEngine()->close() && flushed)
diff --git a/src/corelib/io/qresource.cpp b/src/corelib/io/qresource.cpp
index 3d54969..adfbb15 100644
--- a/src/corelib/io/qresource.cpp
+++ b/src/corelib/io/qresource.cpp
@@ -1285,7 +1285,7 @@ bool QResourceFileEngine::close()
 
 bool QResourceFileEngine::flush()
 {
-    return false;
+    return true;
 }
 
 qint64 QResourceFileEngine::read(char *data, qint64 len)