Hi All,
I'm seeing a race when using "losetup -f file". Some research pointed me to a 2007 path that introduced a "retry" mechanism if the module returned EBUSY. At some point before the project went into git.kernel.org this commit went away.
Can anyone clarify? I'm currently flock()ing /var/lock/losetup outside calls to losetup.
Objections to a losetup patch to do that internally?
Easy repro: for i in {1..100}; do losetup -f image & done
Then check out the output of "losetup -a"
Thanks,
Felipe--
To unsubscribe from this list: send the line "unsubscribe util-linux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
