> ok. The TID+signal approach i mentioned in the other reply should work.
Not sure if a signal is good for this. It might conflict with existing strange historical semantics. > If it's frequent enough we could make this an explicit > sys_async_cancel(TID) API. Ideally there should be a new function like signal_pending() that checks for this. Then the network fs could check those in their blocking loops and error out. Then it would even work on non intr NFS mounts. -Andi - 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/
