On 10/3/22 16:56, Luis Chamberlain wrote:
Yeah I've gone ahead and re-read your original patch again the issue
with that is it waits *once* for the refcnt to go to 0, but that does
not forbit it from going back up, at which point you have a race which
can still create the situation. Every subsystem is different, but for
instance simply running a loop opening a device block file should
suffice to bump the refcnt of a respective block driver module. So
at least the patch itself won't ultimately address this issue I'm
afraid.
Hi Luis,
Thanks for the feedback. I will try to find a solution that does not
require to modify the kernel module code.
Bart.
