> Btw, what we can do is delay closing the actual revoked file until the > task terminates. This has the unfortunate side-effect that a task has > no way of freeing the resources now. But, I am beginning to think it's > not a big problem because the inode mapping will be zapped immediately > upon revoke anyway...
Actually you can't entirely do this. The revoke() definition states explicitly that the driver close occurs at the point of revoke() not later. That can however be pushed into the device revoke method for the cases where it might matter (eg tty). Alan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
