1. 15 1月, 2015 1 次提交
  2. 16 12月, 2014 3 次提交
  3. 14 10月, 2014 6 次提交
  4. 06 5月, 2014 1 次提交
  5. 27 3月, 2014 1 次提交
  6. 09 3月, 2014 1 次提交
  7. 25 2月, 2014 1 次提交
    • J
      qemu_file: use fwrite() correctly · aded6539
      Juan Quintela 提交于
      fwrite() returns the number of items written.  But when there is one
      error, it can return a short write.
      
      In the particular bug that I was tracking, I did a migration to a
      read-only filesystem.  And it was able to finish the migration
      correctly.  fwrite() never returned a negative error code, nor zero,
      always 4096. (migration writes chunks of about 14000 bytes).  And it
      was able to "complete" the migration with success (yes, reading the
      file was a bit more difficult).
      
      To add insult to injury, if your amount of memory was big enough (12GB
      on my case), it overwrote some important structure, and from them,
      malloc failed.  This check makes the problem go away.
      Signed-off-by: NJuan Quintela <quintela@redhat.com>
      Reviewed-by: NEric Blake <eblake@redhat.com>
      Reviewed-by: NMarkus Armbruster <armbru@redhat.com>
      Signed-off-by: NJuan Quintela <quintela@redhat.com>
      aded6539
  8. 13 1月, 2014 1 次提交