On Thu, 06 Aug 2009, Eric Paris wrote: > just work. The whole reason for the timeout is because I don't trust > userspace not to get it wrong and I'd rather not lose my box because of > it. IMO this has nothing to do with userspace(*) and everything to do with complexity. Virus scanning is complex and any such code, whether runing in userspace or not, can easily screw up and freeze the system. The way to solve that is not to implement hacks on the kernel interface, but rather by separating the complex parts and implementing a simple watchdog layer on top of that, that makes sure things don't go wrong. (*) We _must_ trust privileged userspace not to screw up. System scripts can easily do much worse damage than freezing filesystem operations. Just think "rm -rf /". Thanks, Miklos -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
