[lkml]   [2000]   [Aug]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH] thread wakeup fix for 2.4.0-test7
    In article <>,
    <> wrote:
    >User references must be counted separately.

    Sorry, Alexey, but you're just wrong.

    The behaviour you seem to advocate is stupid.

    End of story.

    >Actually, Linus seems to forget about his own idea
    >of returning valid error from close(). Think, how it is possible
    >to return valid error, when fput() is used to close file.

    Bzzt. Wrong answer.

    My claim is that a user program that does a close() on a file that is in
    use is inherently racy. Is that so hard to understand?

    I'm basically saying: if you want reliable behaviour, you should make
    sure in user land that you don't close a file descriptor that is in use
    somewhere else. Linux _will_ give you reliable and dependable semantics
    even if you close() on an fd while it is in use, but I still claim that
    you should not do it.

    EXACTLY because you lose the error information, if for no other reason.

    Imagine that another thread is doing a write() on the fd at the same
    time as your thread is doing a close(). I claim that that is a stupid
    thing to do, and that you shouldn't do it. Linux makes certain that the
    kernel is internally consistent, and you might even choose to depend on
    that internal consistency, but your program is doing things it shouldn't
    be doing.

    You'll lose the errors from the operation, for example. Tough. I'm not
    "forgetting" anything. I'm claiming that it's a "Don't do that then"

    And I'm right. I'm always right, but in this case I'm just a bit more
    right than I usually am.

    Just don't close a file descriptor while it is in use. It's that simple.

    (I'm also claiming that Linux will give the most reasonable possible
    semantics for the case where you _do_ close the file desciptor when it
    is in use. I still claim that you shouldn't do it.)

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

     \ /
      Last update: 2005-03-22 12:38    [W:0.028 / U:42.292 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site