On Thu, 2018-07-26 at 06:35 -0700, Tejun Heo wrote: +AD4- Making removal asynchronous this way sometimes causes issues because +AD4- whether the user sees the device released or not is racy. Hello Tejun, How could this change cause any user-visible changes? My understanding is that any work queued with task+AF8-work+AF8-add() is executed before system call execution leaves kernel context and returns back to user space context. Thanks, Bart.
