[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v4 3/3] backup: don't acquire aio_context in backup_clean
From: |
Max Reitz |
Subject: |
Re: [PATCH v4 3/3] backup: don't acquire aio_context in backup_clean |
Date: |
Thu, 2 Apr 2020 14:59:15 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 |
On 01.04.20 10:15, Stefan Reiter wrote:
> All code-paths leading to backup_clean (via job_clean) have the job's
> context already acquired. The job's context is guaranteed to be the same
> as the one used by backup_top via backup_job_create.
>
> Since the previous logic effectively acquired the lock twice, this
> broke cleanup of backups for disks using IO threads, since the BDRV_POLL_WHILE
> in bdrv_backup_top_drop -> bdrv_do_drained_begin would only release the lock
> once, thus deadlocking with the IO thread.
>
> This is a partial revert of 0abf2581717a19.
>
> Signed-off-by: Stefan Reiter <address@hidden>
> ---
>
> With the two previous patches applied, the commit message should now hold
> true.
>
> block/backup.c | 4 ----
> 1 file changed, 4 deletions(-)
Reviewed-by: Max Reitz <address@hidden>
signature.asc
Description: OpenPGP digital signature