Am 13.03.2025 um 12:53 hat Markus Armbruster geschrieben:
> Kevin Wolf writes:
>
> > Am 12.03.2025 um 15:37 hat Markus Armbruster geschrieben:
> >> bdrv_activate() returns failure without setting an error when
> >> !bs->drv. This is suspicious. Turns out it used to succeed then,
> >> until comm
Am 12.03.2025 um 15:37 hat Markus Armbruster geschrieben:
> bdrv_activate() returns failure without setting an error when
> !bs->drv. This is suspicious. Turns out it used to succeed then,
> until commit 5416645fcf82 changed it to return -ENOMEDIUM.
>
> Return zero instead.
>
> Fixes: 5416645fc
Kevin Wolf writes:
> Am 12.03.2025 um 15:37 hat Markus Armbruster geschrieben:
>> bdrv_activate() returns failure without setting an error when
>> !bs->drv. This is suspicious. Turns out it used to succeed then,
>> until commit 5416645fcf82 changed it to return -ENOMEDIUM.
>>
>> Return zero in
Butterfingers, please ignore this one. I'll send a real reply soon.
Kevin Wolf writes:
> Am 12.03.2025 um 15:37 hat Markus Armbruster geschrieben:
>> bdrv_activate() returns failure without setting an error when
>> !bs->drv. This is suspicious. Turns out it used to succeed then,
>> until commit 5416645fcf82 changed it to return -ENOMEDIUM.
>>
>> Return zero in
bdrv_activate() returns failure without setting an error when
!bs->drv. This is suspicious. Turns out it used to succeed then,
until commit 5416645fcf82 changed it to return -ENOMEDIUM.
Return zero instead.
Fixes: 5416645fcf82 (block: return error-code from bdrv_invalidate_cache)
Signed-off-by:
