4 Feb
2025
4 Feb
'25
1:42 a.m.
On Thu, 30 Jan 2025 19:33:28 +1100
David Gibson
Currently we call repair_sock_init() immediately before tap_sock_unix_init(). However, this means it will be skipped if the vhost-user control fd is passed with --fd instead of being created at a specific path.
That's intended, because we might not have a path in that case. See conf_open_files(). I know it's not perfectly consistent, but it's practical at the moment. The alternative opens up complicated questions such as: should we have a --fd-repair option? What should be the default path if only --fd is given? This is really unnecessary right now. -- Stefano