All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Schiffer <pschiffe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Lukas Czerner <lczerner-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH] close.2: Mention a need of shutdown before closing socket
Date: Tue, 12 Feb 2013 19:41:40 +0100	[thread overview]
Message-ID: <511A8CE4.1090603@redhat.com> (raw)

ping Michael

On Fri, 7 Oct 2011, Michael Kerrisk wrote:
 > Hi Lukas
 >
 > On Fri, Oct 7, 2011 at 9:09 AM, Lukas Czerner <lczerner@> wrote:
 >> On Fri, 7 Oct 2011, Michael Kerrisk wrote:
 >>
 >>> Lukas,
 >>>
 >>> On Mon, Aug 29, 2011 at 2:26 PM, Lukas Czerner <lczerner@...> wrote:
 >>>> When dealing with sockets, we have to be sure that there is no recv
 >>>> still blocking on it on another thread, otherwise it might block
 >>>> forever, since no more messages will be send via the socket. We
 >>>> should advice to use shutdown before closing socket.
 >>>
 >>> I'm looking into this now. The picture may be more complex than
 >>> this. Tell me, so you have a Solaris system available for testing?
 >>>
 >>> Thanks,
 >>
 >> Hi Michael,
 >>
 >> Thanks for looking into this. Unfortunately I do not have any
 >> Solaris system for testing, that was a customer report. His
 >> complaint was mainly not because the behaviour on Linux differs, but
 >> because this was not documented anywhere.
 >
 > Okay. I will see if I can find a test system somewhere. (The system I
 > used to use seems to have gone away.)
 >
 > Just FYI: I confirmed what you are seeing, but the issue seems more
 > general: basically, closing a file descriptor in one thread while
 > reading in another thread does not cause the read operation to
 > terminate (it will still read data if/when it becomes available).
 >
 > By the way, I'm wondering about creating a small repo of test
 > programs. I might like to add a modified version of your test program
 > to that repo. Can you put that code under a Free License and supply a
 > copyright?
 >
 > Thanks,
 >
 > Michael

Hi Michael,

no problem, here is the program, feel free to update it as you like.
Thanks for looking into this.

-Lukas
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2013-02-12 18:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-12 18:41 Peter Schiffer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-08-29 12:26 [PATCH] close.2: Mention a need of shutdown before closing socket Lukas Czerner
     [not found] ` <1314620800-15587-1-git-send-email-lczerner-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-09-01  8:43   ` Lukas Czerner
     [not found]     ` <alpine.LFD.2.00.1109011043050.3665-D5fXUWdM4RC5eBp5B7zZTR/sF2h8X+2i0E9HWUfgJXw@public.gmane.org>
2011-09-07 15:54       ` Lukas Czerner
2011-09-10 13:59   ` Michael Kerrisk
     [not found]     ` <CAKgNAkj_+h9njO6ffVg_1ckpBLdyHM=6iZyyU1jpL5sY6Zrs2Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-09-12 10:25       ` Lukas Czerner
     [not found]         ` <alpine.LFD.2.00.1109121215310.3888-D5fXUWdM4RC5eBp5B7zZTR/sF2h8X+2i0E9HWUfgJXw@public.gmane.org>
2011-09-22  9:36           ` Lukas Czerner
2011-10-07  6:28   ` Michael Kerrisk
     [not found]     ` <CAKgNAkjDZufWp-H7NeSRT40FGBRCkMuisesbGcdJnD94OZucUA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-10-07  7:09       ` Lukas Czerner
     [not found]         ` <alpine.LFD.2.00.1110070906440.7183-D5fXUWdM4RC5eBp5B7zZTR/sF2h8X+2i0E9HWUfgJXw@public.gmane.org>
2011-10-07 10:34           ` Michael Kerrisk
     [not found]             ` <CAKgNAki_fBFgoOHwsBbhocpzRt3_Zges49mLQwpkHfA+NYcxHA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-10-07 11:03               ` Lukas Czerner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=511A8CE4.1090603@redhat.com \
    --to=pschiffe-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=lczerner-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.