On Thu, Dec 1, 2011 at 18:10, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> wrote: > On Thu, Dec 1, 2011 at 6:27 AM, Matthew Wilcox <matthew@xxxxxx> wrote: >> >> Another problem scenario is an NFS mounted file going away while the >> user is writing to it. The user should be able to kill the stuck process >> without rebooting their machine. > > Well, NFS has always had the 'intr' mount option. For some values of always; My nfs(5) manpage says: "The intr / nointr mount option is deprecated after kernel 2.6.25. Only SIGKILL can interrupt a pending NFS operation on these kernels, and if specified, this mount option is ignored to provide backwards compatibility with older kernels." (Apparently this was related to the introduction of TASK_KILLABLE.) Isn't this pretty much the same "common sense" semantics that Jan's patch is introducing? Wu's testing in this thread suggests that at some point this TASK_KILLABLE for nfs writer thing was broken, or didn't work very robustly to begin with? Anyway, awesome if it's getting fixed, not only for NFS but for all regular files! -- Janne Blomqvist -- 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
