On Mon, 05/15 16:02, Peter Lieven wrote:
> > > do you have a pointer to the image locking mechanism?
> > It hit qemu.git master just a moment ago. See raw_check_perm.
> 
> which master are you looking at?
> 
> $ git fetch upstream
> $ git log upstream/master --oneline
> 3a87606 Merge tag 'tracing-pull-request' into staging
> b54933e Merge tag 'block-pull-request' into staging
> 3753e25 Merge remote-tracking branch 'kwolf/tags/for-upstream' into staging
> 5651743 trace: add sanity check
> 321d1db aio: add missing aio_notify() to aio_enable_external()
> ee29d6a block: Simplify BDRV_BLOCK_RAW recursion
> 33c53c5 coroutine: remove GThread implementation
> ecc1f5a maintainers: Add myself as linux-user reviewer
> d541e20 Merge remote-tracking branch 'mreitz/tags/pull-block-2017-05-11' into 
> queue-block
> 8dd30c8 MAINTAINERS: Add qemu-progress to the block layer
> d2cb36a qcow2: Discard/zero clusters by byte count
> f10ee13 qcow2: Assert that cluster operations are aligned
> fbaa6bb qcow2: Optimize write zero of unaligned tail cluster
> e249d51 iotests: Add test 179 to cover write zeroes with unmap
> d9ca221 iotests: Improve _filter_qemu_img_map
> 06cc5e2 qcow2: Optimize zero_single_l2() to minimize L2 churn
> fdfab37 qcow2: Make distinction between zero cluster types obvious
> 3ef9521 qcow2: Name typedef for cluster type
> 4341df8 qcow2: Correctly report status of preallocated zero clusters
> 4c41cb4 block: Update comments on BDRV_BLOCK_* meanings

It's 244a5668 "file-posix: Add image locking to perm operations".

Fam

Reply via email to