[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v6 3/5] migration: process_incoming_migration_co(): fix repor
|
From: |
Fabiano Rosas |
|
Subject: |
Re: [PATCH v6 3/5] migration: process_incoming_migration_co(): fix reporting s->error |
|
Date: |
Tue, 30 Apr 2024 11:29:25 -0300 |
Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru> writes:
> It's bad idea to leave critical section with error object freed, but
> s->error still set, this theoretically may lead to use-after-free
> crash. Let's avoid it.
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
Reviewed-by: Fabiano Rosas <farosas@suse.de>
- [PATCH v6 0/5] migration: do not exit on incoming failure, Vladimir Sementsov-Ogievskiy, 2024/04/30
- [PATCH v6 3/5] migration: process_incoming_migration_co(): fix reporting s->error, Vladimir Sementsov-Ogievskiy, 2024/04/30
- Re: [PATCH v6 3/5] migration: process_incoming_migration_co(): fix reporting s->error,
Fabiano Rosas <=
- [PATCH v6 5/5] qapi: introduce exit-on-error parameter for migrate-incoming, Vladimir Sementsov-Ogievskiy, 2024/04/30
- [PATCH v6 4/5] migration: process_incoming_migration_co(): rework error reporting, Vladimir Sementsov-Ogievskiy, 2024/04/30
- [PATCH v6 2/5] migration: process_incoming_migration_co(): complete cleanup on failure, Vladimir Sementsov-Ogievskiy, 2024/04/30
- [PATCH v6 1/5] migration: move trace-point from migrate_fd_error to migrate_set_error, Vladimir Sementsov-Ogievskiy, 2024/04/30