You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When kbus is built into the kernel, i.e. not as a module, there is (at present)
no way to have it expire unused unloved devices. This leads to some test
failures, which are expecting to be able to rmmod and have them go away.
We might fix this by having the RESET ioctl clean up and remove all but kbus0?
I suppose it ought to require some sort of priviliges, e.g. current_uid()==0.
Original issue reported on code.google.com by [email protected] on 12 Jan 2011 at 4:55
The text was updated successfully, but these errors were encountered:
We might also decide that it makes no sense to build kbus as a module, in which
case we'd want to put "depends on m" in its Kconfig entry. However I am not
convinced of this.
This does sound like the (long awaited) sensible use for the RESET ioctl.
Clearly the tests need fixing as well, though (I'll try to have a look at them).
Original issue reported on code.google.com by
[email protected]
on 12 Jan 2011 at 4:55The text was updated successfully, but these errors were encountered: