lkml.org 
[lkml]   [2002]   [Aug]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: manipulating sigmask from filesystems and drivers

    On Thu, 1 Aug 2002, Roman Zippel wrote:

    > > Go read the standards. Some IO is not interruptible.
    >
    > Which standard? Which "some IO"?

    Any regular file IO is supposed to give you the full result.

    If you write() to a file, and get a partial return value back due to a
    signal, there are programs that will assume that the disk is full (there
    are also programs that will just lose your data).

    This is not "sloppy programming". See the read() system call manual, which
    says

    Upon successful completion, read(), readv(), and pread() return the num-
    ber of bytes actually read and placed in the buffer. The system guaran-
    tees to read the number of bytes requested if the descriptor references a
    normal file that has that many bytes left before the end-of-file, but in
    no other case.

    Note the "The system guarantees to read the number of bytes requested .."
    part.

    Stop arguing about this. It's a FACT.

    Linus

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-03-22 13:27    [W:3.023 / U:0.032 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site