Re: [Qemu-devel] [PATCH for-4.1] util/hbitmap: update orig_size on truncate

2019-08-05 Thread Max Reitz
On 05.08.19 14:01, Vladimir Sementsov-Ogievskiy wrote: > Without this, hbitmap_next_zero and hbitmap_next_dirty_area are broken > after truncate. So, orig_size is broken since it's introduction in > 76d570dc495c56bb. > > Fixes: 76d570dc495c56bb > Signed-off-by: Vladimir Sementsov-Ogievskiy Thank

Re: [Qemu-devel] [PATCH for-4.1] util/hbitmap: update orig_size on truncate

2019-08-05 Thread Paolo Bonzini
On 05/08/19 14:19, Max Reitz wrote: > On 05.08.19 14:01, Vladimir Sementsov-Ogievskiy wrote: >> Without this, hbitmap_next_zero and hbitmap_next_dirty_area are broken >> after truncate. So, orig_size is broken since it's introduction in >> 76d570dc495c56bb. >> >> Fixes: 76d570dc495c56bb >> Signed-o

Re: [Qemu-devel] [PATCH for-4.1] util/hbitmap: update orig_size on truncate

2019-08-05 Thread Max Reitz
On 05.08.19 14:01, Vladimir Sementsov-Ogievskiy wrote: > Without this, hbitmap_next_zero and hbitmap_next_dirty_area are broken > after truncate. So, orig_size is broken since it's introduction in > 76d570dc495c56bb. > > Fixes: 76d570dc495c56bb > Signed-off-by: Vladimir Sementsov-Ogievskiy > ---

[Qemu-devel] [PATCH for-4.1] util/hbitmap: update orig_size on truncate

2019-08-05 Thread Vladimir Sementsov-Ogievskiy
Without this, hbitmap_next_zero and hbitmap_next_dirty_area are broken after truncate. So, orig_size is broken since it's introduction in 76d570dc495c56bb. Fixes: 76d570dc495c56bb Signed-off-by: Vladimir Sementsov-Ogievskiy --- Hi! Here is one more hbitmap bug I noticed. It's my fault, I'm sorr