Sato-san, > > What you *could* do is to start putting processes to sleep if they > > attempt to write to the frozen filesystem, and then detect the > > deadlock case where the process holding the file descriptor used to > > freeze the filesystem gets frozen because it attempted to write to the > > filesystem --- at which point it gets some kind of signal (which > > defaults to killing the process), and the filesystem is unfrozen and > > as part of the unfreeze you wake up all of the processes that were put > > to sleep for touching the frozen filesystem. > > I don't think close() usually writes to journal and the deadlock occurs. > Is there the special case which close() writes to journal in case of > getting signal? I am afraid that Ted-san is concerning about the fact that the freeze program can touch the target filesystem by mistake (rather than just close() and its journal behavior) # cd /mnt # freeze /mnt > ./logfile This is more unclear to admins than "rm -rf /" case. So we need to implement some bail-out mechanism as he pointed out, such that if kernel noticed that the freezer is trying to touch the target filesystem, kernel would kill the freezer and automatically unfreeze the filesystem again. Regards, - 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
