[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v2 5/5] migration: Move the yank unregister of channel_close
From: |
Peter Xu |
Subject: |
Re: [PATCH v2 5/5] migration: Move the yank unregister of channel_close out |
Date: |
Thu, 22 Jul 2021 12:19:14 -0400 |
On Thu, Jul 22, 2021 at 04:27:35PM +0100, Dr. David Alan Gilbert wrote:
> > @@ -3352,6 +3355,8 @@ static MigThrError postcopy_pause(MigrationState *s)
> >
> > /* Current channel is possibly broken. Release it. */
> > assert(s->to_dst_file);
> > + /* Unregister yank for current channel */
> > + migration_ioc_unregister_yank_from_file(s->to_dst_file);
>
> Should this go inside the lock?
Shouldn't need to; as we've got the assert() right above so otherwise we'll
abrt otherwise :)
The mutex lock/unlock right below this one is not protecting us from someone
changing it but really for being able to wait until someone finished using it
then we won't crash someone else.
I think the rational is to_dst_file is managed by migration thread while
from_dst_file is managed by rp_thread.
Maybe I add a comment above?
Thanks,
--
Peter Xu
- [PATCH v2 1/5] migration: Fix missing join() of rp_thread, (continued)
- [PATCH v2 1/5] migration: Fix missing join() of rp_thread, Peter Xu, 2021/07/21
- [PATCH v2 2/5] migration: Make from_dst_file accesses thread-safe, Peter Xu, 2021/07/21
- [PATCH v2 3/5] migration: Introduce migration_ioc_[un]register_yank(), Peter Xu, 2021/07/21
- [PATCH v2 4/5] migration: Teach QEMUFile to be QIOChannel-aware, Peter Xu, 2021/07/21
- [PATCH v2 5/5] migration: Move the yank unregister of channel_close out, Peter Xu, 2021/07/21