On Tue, 03 Jun 2025 17:38:33 -0600, Uday Shankar wrote:
Some failure modes are handled poorly by kublk. For example, if ublk_drv is built as a module but not currently loaded into the kernel, ./kublk add ... just hangs forever. This happens because in this case (and a few others), the worker process does not notify its parent (via a write to the shared eventfd) that it has tried and failed to initialize, so the parent hangs forever. Fix this by ensuring that we always notify the parent process of any initialization failure, and have the parent print a (not very descriptive) log line when this happens.
[...]
Applied, thanks!
[1/1] selftests: ublk: kublk: improve behavior on init failure commit: a2f4c1ae163b815dc81e3cab97c3149fdc6639e3
Best regards,