public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "teodori.serge at hotmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/13660] poll wrong revents returned
Date: Thu, 09 Feb 2012 22:42:00 -0000	[thread overview]
Message-ID: <bug-13660-131-ORy5TDijEK@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13660-131@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=13660

--- Comment #5 from Teodori Serge <teodori.serge at hotmail dot com> 2012-02-09 22:41:29 UTC ---
Ok after testing this on Windows and Solaris, I found that only Linux is
handling this in a different manner. Linux set POLLIN if peer closes
connection, and the next recv() will return zero bytes received. This is also a
good method to intercept a hangup. Well then there is no bug, but Linux should
handle this correctly like Windows and Solaris, because it is called a POSIX
function (whicj means Portable Operating System...)
Anyway where can I find someone from the kernel team? Any idea, perhaps anyone
can correct it? Is there also a forum for the kernel developer?
http://www.kernel.org/ doesn't seem to have one.
And thank you again.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  parent reply	other threads:[~2012-02-09 22:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-03 19:14 [Bug libc/13660] New: " teodori.serge at hotmail dot com
2012-02-03 19:47 ` [Bug libc/13660] " drepper.fsp at gmail dot com
2012-02-04  0:08 ` bugdal at aerifal dot cx
2012-02-09  0:19 ` teodori.serge at hotmail dot com
2012-02-09  0:42 ` bugdal at aerifal dot cx
2012-02-09 22:42 ` teodori.serge at hotmail dot com [this message]
2012-02-10  1:29 ` bugdal at aerifal dot cx
2014-06-13 14:09 ` fweimer at redhat dot com

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-13660-131-ORy5TDijEK@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).