Bug fixes for gluster
Status from this message: Applied to my block branch:
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v3 Latest3 patches 1 replyApplied
- v23 patches 12 repliesSuperseded
- v12 patches 15 repliesSuperseded
Patches in v3 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | block/gluster: return correct error valueblock/ | +1 | 0 replies | |
| 2/3 | block/gluster: code movement of qemu_gluster_close()block/ | +11 | 0 replies | |
| 3/3 | block/gluster: prevent data loss after i/o errorblock/ configure | +60 | 0 replies |
Reviews trailers per patch
1 of 3 patches has a Reviewed-by or Acked-by.
| Patch | Niels de Vos |
|---|---|
| 1/3 | R-b |
| 2/3 | |
| 3/3 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [Qemu-devel] [PATCH for-2.6 v3 0/3] Bug fixes for gluster
Change from v2:
Look at the error return from the aio callback from fsync, as well. (thanks Kevin)
Bug fixes for gluster; third patch is to prevent a potential data loss when trying to recover from a recoverable error (such as ENOSPC).
The final patch closes the gluster fd and sets the protocol drv to NULL on fsync failure in gluster; we have no way of knowing what gluster versions support retaining fysnc cache on error, so until we do the safest thing to do is invalidate the drive.
Jeff Cody (3):
block/gluster: return correct error value block/gluster: code movement of qemu_gluster_close() block/gluster: prevent data loss after i/o error
block/gluster.c | 77 +++++++++++++++++++++++++++++++++++++++++++++++---------- configure | 8 ++++++ 2 files changed, 72 insertions(+), 13 deletions(-)
Signature · 1 line
1.9.3