| commit | 3a8b81f2e6393828589699bb0b8ef557b9ae5937 | |
| author | Fiona Ebner <f.ebner@proxmox.com> | |
| Fri, 26 May 2023 11:59:08 +0000 (26 13:59 +0200) | ||
| committer | Juan Quintela <quintela@redhat.com> | |
| Thu, 1 Jun 2023 23:03:19 +0000 (2 01:03 +0200) | ||
| tree | 7c91e7b712aab60cdf08bb7516b05036671ff192 | treesnapshot (tar.gz zip) |
| parent | a4c6275aa11f153a6a7e614dd867c62b904f8838 | commitdiff |
migration: stop tracking ram writes when cancelling background migration
Currently, it is only done when the iteration finishes successfully.
Not cleaning up the userfaultfd write protection can lead to
symptoms/issues such as the process hanging in memmove or GDB not
being able to attach.
Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
Message-Id: <20230526115908.196171-1-f.ebner@proxmox.com>
Signed-off-by: Juan Quintela <quintela@redhat.com>
Currently, it is only done when the iteration finishes successfully.
Not cleaning up the userfaultfd write protection can lead to
symptoms/issues such as the process hanging in memmove or GDB not
being able to attach.
Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
Message-Id: <20230526115908.196171-1-f.ebner@proxmox.com>
Signed-off-by: Juan Quintela <quintela@redhat.com>
| migration/migration.c | diffblobblamehistory |