Re: [PATCH v2 09/10] block: Let replace_child_noperm free children

2021-11-16 Thread Vladimir Sementsov-Ogievskiy
15.11.2021 16:04, Hanna Reitz wrote: On 12.11.21 17:10, Vladimir Sementsov-Ogievskiy wrote: 11.11.2021 15:08, Hanna Reitz wrote: In most of the block layer, especially when traversing down from other BlockDriverStates, we assume that BdrvChild.bs can never be NULL.  When it becomes NULL, it is

Re: [PATCH v2 09/10] block: Let replace_child_noperm free children

2021-11-15 Thread Hanna Reitz
On 12.11.21 17:10, Vladimir Sementsov-Ogievskiy wrote: 11.11.2021 15:08, Hanna Reitz wrote: In most of the block layer, especially when traversing down from other BlockDriverStates, we assume that BdrvChild.bs can never be NULL.  When it becomes NULL, it is expected that the corresponding

Re: [PATCH v2 09/10] block: Let replace_child_noperm free children

2021-11-12 Thread Vladimir Sementsov-Ogievskiy
11.11.2021 15:08, Hanna Reitz wrote: In most of the block layer, especially when traversing down from other BlockDriverStates, we assume that BdrvChild.bs can never be NULL. When it becomes NULL, it is expected that the corresponding BdrvChild pointer also becomes NULL and the BdrvChild object

[PATCH v2 09/10] block: Let replace_child_noperm free children

2021-11-11 Thread Hanna Reitz
In most of the block layer, especially when traversing down from other BlockDriverStates, we assume that BdrvChild.bs can never be NULL. When it becomes NULL, it is expected that the corresponding BdrvChild pointer also becomes NULL and the BdrvChild object is freed. Therefore, once