buglwIP - A Lightweight TCP/IP stack - Bugs: bug #20155, select() with errorfd set

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #20155: select() with errorfd set

Submitted by:  Srinivas Gollakota <gollakota>
Submitted on:  Tue 12 Jun 2007 02:57:02 PM UTC  
 
Category: sockets/netconnSeverity: 1 - Wish
Item Group: Feature RequestStatus: Fixed
Privacy: PublicAssigned to: Simon Goldschmidt <goldsimon>
Open/Closed: ClosedPlanned Release: None
lwIP version: CVS Head

Fri 29 Jan 2010 11:07:27 PM UTC, comment #5:

Checked in patch #6860 - this should be done now.

Simon Goldschmidt <goldsimon>
Project AdministratorIn charge of this item.
Sat 22 Aug 2009 10:08:58 PM UTC, comment #4:

There seems to be a patch for this:
patch #6860: Add non-blocking support for connect, and except set support in select

Simon Goldschmidt <goldsimon>
Project AdministratorIn charge of this item.
Thu 28 Jun 2007 10:58:28 AM UTC, comment #3:

Can we collect a list of which events should lead to setting the error fd set?

- tcp_pcb->err() is called
- connect failed?
- I can not think about udp or raw errors...

http://www.opengroup.org/onlinepubs/000095399/functions/select.html says:
"A socket shall be considered to have an exceptional condition pending if a receive operation with O_NONBLOCK clear for the open file description and with the MSG_OOB flag set would return out-of-band data without blocking. (It is protocol-specific whether the MSG_OOB flag would be used to read out-of-band data.) A socket shall also be considered to have an exceptional condition pending if an out-of-band data mark is present in the receive queue. Other circumstances under which a socket may be considered to have an exceptional condition pending are protocol-specific and implementation-defined."

Simon Goldschmidt <goldsimon>
Project AdministratorIn charge of this item.
Fri 15 Jun 2007 07:20:11 AM UTC, comment #2:

Integrating the error fd set would be some work since currently the only events passed on to the socket layer are send and receive events. Error events would have to be integrated in api_lib.c/api_msg.c before select/selscan can work with them.

Simon Goldschmidt <goldsimon>
Project AdministratorIn charge of this item.
Tue 12 Jun 2007 03:01:36 PM UTC, comment #1:

This is not the only problem with select. But I don't know if someone will be work on that on the current release...

But if you have a solution, provide it, we will check it and integrate if it's good...

Frédéric Bernon <fbernon>
Project Member
Tue 12 Jun 2007 02:57:02 PM UTC, original submission:

select()/lwip_selscan checks only for read and write fd's not error fd's. If there is a socket error (connection error) then select should report if the socket fd is present in the error fd set.
-Srinivas.

Srinivas Gollakota <gollakota>

 

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by goldsimon (Posted a comment)
  • -unavailable- added by fbernon (Posted a comment)
  • -unavailable- added by gollakota (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 6 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Fri 29 Jan 2010 11:07:27 PM UTCgoldsimonStatusPostponed=>Fixed
      Assigned toNone=>goldsimon
      Open/ClosedOpen=>Closed
    Sat 22 Aug 2009 10:09:30 PM UTCgoldsimonPlanned Release=>1.4.0
    Tue 10 Jul 2007 07:28:09 PM UTCgoldsimonSeverity3 - Normal=>1 - Wish
    Thu 21 Jun 2007 08:20:03 PM UTCgoldsimonStatusNone=>Postponed

    Back to the top


    Powered by Savane 3.1-cleanup1