[lkml]   [2011]   [Dec]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH] fs: Make write(2) interruptible by a fatal signal
    On Thu, Dec 1, 2011 at 6:27 AM, Matthew Wilcox <> 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.

    The problem with NFS and 'intr' is that it's very user-visible, and
    makes even nonfatal signals cause EINTR. So the "abort writes on fatal
    signals" is a lot less noticeable to any programs: sure, it does
    introduce potentially visible semantic changes, but now they are
    visible only across different processes, not within one process.

    And anybody who relies on "all or nothing" even in the face of SIGKILL
    is just broken. That said, like so many changes, I think this falls
    solidly on the "we should do this, but if somebody reports a

    I suspect the likelihood of regressions is basically zero. No
    application that actually cares about its data would ever rely on the
    "writes will complete entirely or not at all" semantics. Not only has
    it never been true on NFS, but it's not true in the face of crashes
    either, so any careful app will already depend on other things like
    fsync+rename etc.


    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2011-12-01 17:13    [W:0.020 / U:1.392 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site