lkml.org 
[lkml]   [2002]   [Jul]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: Closing a socket

    > > I have implemented a new socket address family and have noted that
    > > from a multi-threaded application, if a thread calls close(fd) while a
    > > second thread has a blocking read outstanding, the sockets release() is not
    > > called. Is this correct? How can one unblock the read in order to do the
    > > close.
    You might want to implement shutdown(). Thread #1 will call shutdown()
    instead of
    the close(). Your shutdown() implementation can do something like:
    sk->shutdown |= RCV_SHUTDOWN;
    sk->state_change(sk);
    So, reader will wakeup, check shutdown mask and return error because socket was
    shut down.

    Max


    -
    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:4.914 / U:0.036 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site