Fork us on GitHub Follow us on Google+ Follow us on Facebook Follow us on Twitter

Opened 6 years ago

Last modified 5 months ago

#448 new enhancement

Forced vs. non-forced administrative device removal

Reported by: Jiri Svoboda Owned by:
Priority: major Milestone:
Component: helenos/unspecified Version: mainline
Keywords: Cc:
Blocker for: Depends on:
See also: #383


Similar to an unmount operation, administrative device removal (devctl offline) can be forced or non-forced. Non-forced removal will fail if there are any clients connected to an exposed function [of some child of a nexus device]. Forced removal must succeed even if there are active clients.

Extend DDF to distinguish between forced an non-forced removal (e.g. by adding a simple flag to the relevant calls).

Ideally all drivers should support both. Forced removal is slightly trickier, because it must succeed at any time, even if the driver is actively processing some transactions.

Change History (1)

comment:1 Changed 5 months ago by Jakub Jermář

What needs to be done in this regards? Some drivers probably still don't support either, but some do as well as DDF does.

Note: See TracTickets for help on using tickets.