linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org
To: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [Bug 40852] New: select(2): document action of close()'ing a fd during a select()
Date: Wed, 10 Aug 2011 13:28:25 GMT	[thread overview]
Message-ID: <bug-40852-11311@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=40852

           Summary: select(2): document action of close()'ing a fd during
                    a select()
           Product: Documentation
           Version: unspecified
    Kernel Version: n/a
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: man-pages
        AssignedTo: documentation_man-pages-ztI5WcYan/vQLgFONoPN62D2FQJk+8+b@public.gmane.org
        ReportedBy: fillods-iA+eEnwkJgzk1uMJSBkQmQ@public.gmane.org
        Regression: No


I had a hard time figuring out what is the Linux's expected behavior of
select() syscall when a file descriptor is close()'d in the meantime. The man
page 3.27-1ubuntu2 lacks this piece of information. This is on Ubuntu 11.04.

Like many other OS, I would have expect select() to bail out on Linux, but it
is not the case. When some other thread close() a file descriptor currently
watched by select(), Linux does not make the select() syscall to return with
errno=EBADF, it simply ignores it and does not return.
Please note that this behavior is undefined in POSIX. 

IMO, this has to be appropriately documented in the select(2) man page.

Maybe something like "The select() system call never returns if a file
descriptor is closed in the meantime. This behavior is undefined in POSIX".[3]

Rem: this case is not to be confused with a file that has already been closed
before calling select().

Background:

[1]
http://stackoverflow.com/questions/543541/what-does-select2-do-if-you-close2-a-file-descriptor-in-a-separate-thread/543595#543595

[2] http://lkml.indiana.edu/hypermail/linux/kernel/0106.0/0768.html

[3]
https://lists.linux-foundation.org/pipermail/bugme-new/2003-April/008335.html

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
--
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:[~2011-08-10 13:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-10 13:28 bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r [this message]
     [not found] ` <bug-40852-11311-3bo0kxnWaOQUvHkbgXJLS5sdmw4N0Rt+2LY78lusg7I@public.gmane.org/>
2012-08-17  5:45   ` [Bug 40852] select(2): document action of close()'ing a fd during a select() bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
2012-08-17  6:30   ` bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
2012-08-17  6:38   ` bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
2012-08-17  6:42   ` bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r

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=bug-40852-11311@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon-590eeb7gvniway/ihj7yzeb+6bgklq7r@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).