qemu-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-commits] [qemu/qemu] d4d3e5: block: Fix parameter checking in bdrv


From: GitHub
Subject: [Qemu-commits] [qemu/qemu] d4d3e5: block: Fix parameter checking in bdrv_co_copy_rang...
Date: Tue, 03 Jul 2018 05:49:55 -0700

  Branch: refs/heads/master
  Home:   https://github.com/qemu/qemu
  Commit: d4d3e5a0d53a57282955e8a3ed7acc1ca90552d9
      
https://github.com/qemu/qemu/commit/d4d3e5a0d53a57282955e8a3ed7acc1ca90552d9
  Author: Fam Zheng <address@hidden>
  Date:   2018-07-02 (Mon, 02 Jul 2018)

  Changed paths:
    M block/io.c

  Log Message:
  -----------
  block: Fix parameter checking in bdrv_co_copy_range_internal

src may be NULL if BDRV_REQ_ZERO_WRITE flag is set, in this case only
check dst and dst->bs. This bug was introduced when moving in the
request tracking code from bdrv_co_copy_range, in 37aec7d75eb.

This especially fixes the possible segfault when initializing src_bs
with a NULL src.

Signed-off-by: Fam Zheng <address@hidden>
Message-id: address@hidden
Reviewed-by: Jeff Cody <address@hidden>
Signed-off-by: Jeff Cody <address@hidden>


  Commit: dee12de89380483656072f775f5ef99f4426f966
      
https://github.com/qemu/qemu/commit/dee12de89380483656072f775f5ef99f4426f966
  Author: Fam Zheng <address@hidden>
  Date:   2018-07-02 (Mon, 02 Jul 2018)

  Changed paths:
    M block/io.c
    M include/block/block.h

  Log Message:
  -----------
  block: Honour BDRV_REQ_NO_SERIALISING in copy range

This semantics is needed by drive-backup so implement it before using
this API there.

Reviewed-by: Stefan Hajnoczi <address@hidden>
Signed-off-by: Fam Zheng <address@hidden>
Message-id: address@hidden
Signed-off-by: Jeff Cody <address@hidden>


  Commit: 9ded4a0114968e98b41494fc035ba14f84cdf700
      
https://github.com/qemu/qemu/commit/9ded4a0114968e98b41494fc035ba14f84cdf700
  Author: Fam Zheng <address@hidden>
  Date:   2018-07-02 (Mon, 02 Jul 2018)

  Changed paths:
    M block/backup.c
    M block/trace-events

  Log Message:
  -----------
  backup: Use copy offloading

The implementation is similar to the 'qemu-img convert'. In the
beginning of the job, offloaded copy is attempted. If it fails, further
I/O will go through the existing bounce buffer code path.

Then, as Kevin pointed out, both this and qemu-img convert can benefit
from a local check if one request fails because of, for example, the
offset is beyond EOF, but another may well be accepted by the protocol
layer. This will be implemented separately.

Reviewed-by: Stefan Hajnoczi <address@hidden>
Signed-off-by: Fam Zheng <address@hidden>
Message-id: address@hidden
Signed-off-by: Jeff Cody <address@hidden>


  Commit: a395717cbd26e7593d3c3fe81faca121ec6d13e8
      
https://github.com/qemu/qemu/commit/a395717cbd26e7593d3c3fe81faca121ec6d13e8
  Author: Peter Maydell <address@hidden>
  Date:   2018-07-03 (Tue, 03 Jul 2018)

  Changed paths:
    M block/backup.c
    M block/io.c
    M block/trace-events
    M include/block/block.h

  Log Message:
  -----------
  Merge remote-tracking branch 'remotes/cody/tags/block-pull-request' into 
staging

# gpg: Signature made Tue 03 Jul 2018 04:42:11 BST
# gpg:                using RSA key BDBE7B27C0DE3057
# gpg: Good signature from "Jeffrey Cody <address@hidden>"
# gpg:                 aka "Jeffrey Cody <address@hidden>"
# gpg:                 aka "Jeffrey Cody <address@hidden>"
# Primary key fingerprint: 9957 4B4D 3474 90E7 9D98  D624 BDBE 7B27 C0DE 3057

* remotes/cody/tags/block-pull-request:
  backup: Use copy offloading
  block: Honour BDRV_REQ_NO_SERIALISING in copy range
  block: Fix parameter checking in bdrv_co_copy_range_internal

Signed-off-by: Peter Maydell <address@hidden>


Compare: https://github.com/qemu/qemu/compare/9b75dcb15f56...a395717cbd26
      **NOTE:** This service been marked for deprecation: 
https://developer.github.com/changes/2018-04-25-github-services-deprecation/

      Functionality will be removed from GitHub.com on January 31st, 2019.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]