> > In that latter case there's a lot of flexibility. Why are you
> > thinking a "remove" might want to get undone?
>
> Would you clarify how you envision a user working with a
> pending remove? Is it an implementation where a long
> period of time might pass before the the device is actually
> removed?
If I understand this correctly, "pending" is a state which indicates
that a physical device has been unplugged, but the connection between
that device's node (and fds) and the driver still exists. At some point
(no more open fds) the driver would be free to break the node <-> driver
relation. If indeed the device is replugged in the pending period the driver
could go back from "pending" to "active". (If there's no state to be lost)
For the user any action on an fd should either yield an error or block.
Probably open should fail.
However I'd like to see the decision to go from pending to gone in the common
core where possible, eg. in the scsi upper layer. The same should be true for
the decision when to return an error to user space.
HTH
Oliver
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
