Re: [PATCH v3 0/3] proper locking on bitmap add/remove paths

2019-09-27 Thread John Snow
On 9/27/19 4:37 AM, Vladimir Sementsov-Ogievskiy wrote: > 26.09.2019 22:01, John Snow wrote: >> >> >> On 9/20/19 4:25 AM, Vladimir Sementsov-Ogievskiy wrote: >>> Hi all! >>> >>> We need to lock qcow2 mutex on accessing in-image metadata, especially >>> on updating this metadata. Let's implement

Re: [PATCH v3 0/3] proper locking on bitmap add/remove paths

2019-09-27 Thread Vladimir Sementsov-Ogievskiy
26.09.2019 22:01, John Snow wrote: > > > On 9/20/19 4:25 AM, Vladimir Sementsov-Ogievskiy wrote: >> Hi all! >> >> We need to lock qcow2 mutex on accessing in-image metadata, especially >> on updating this metadata. Let's implement it. >> >> v3: >> 01: add John's r-b >> 02: - fix bdrv_remove_persi

Re: [PATCH v3 0/3] proper locking on bitmap add/remove paths

2019-09-26 Thread John Snow
On 9/20/19 4:25 AM, Vladimir Sementsov-Ogievskiy wrote: > Hi all! > > We need to lock qcow2 mutex on accessing in-image metadata, especially > on updating this metadata. Let's implement it. > > v3: > 01: add John's r-b > 02: - fix bdrv_remove_persistent_dirty_bitmap return value > - drop e

Re: [PATCH v3 0/3] proper locking on bitmap add/remove paths

2019-09-26 Thread John Snow
On 9/20/19 4:25 AM, Vladimir Sementsov-Ogievskiy wrote: > Hi all! > > We need to lock qcow2 mutex on accessing in-image metadata, especially > on updating this metadata. Let's implement it. > > v3: > 01: add John's r-b > 02: - fix bdrv_remove_persistent_dirty_bitmap return value > - drop e