Skip to content

Conversation

avagin
Copy link
Member

@avagin avagin commented Apr 21, 2025

CRIU is locking the network during restore in an "empty" network namespace. However, "empty" in this context means CRIU isn't restoring the namespace. This network namespace can be the same namespace where processes have been dumped and so the network is already locked in it.

Fixes #2650

CRIU locks the network during restore in an "empty" network namespace.
However, "empty" in this context means CRIU isn't restoring the
namespace. This network namespace can be the same namespace where
processes have been dumped and so the network is already locked in it.

Fixes checkpoint-restore#2650

Signed-off-by: Andrei Vagin <avagin@gmail.com>
@avagin avagin force-pushed the empty-netns-lock branch from b37e572 to 22fdffb Compare April 21, 2025 06:33
Copy link
Member

@adrianreber adrianreber left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks. Looks good. The EEXIST error code on nft table creation makes it easy to see if the table exists. I like that.

@avagin avagin merged commit 75eaa65 into checkpoint-restore:criu-dev Apr 21, 2025
39 of 44 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Possible criu v4.1 regression in Fedora
2 participants