[SSSD] [PATCH] Fixes for client communication

Stephen Gallagher sgallagh at redhat.com
Wed Mar 17 16:06:13 UTC 2010


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/17/2010 08:43 AM, Stephen Gallagher wrote:
> On 03/17/2010 08:30 AM, Sumit Bose wrote:
>> On Wed, Mar 17, 2010 at 01:16:24PM +0100, Sumit Bose wrote:
>>> Hi,
>>>
>>> this patch fixes some issues in the client communication code of the
>>> responders.
>>>
>>> The man pages of send() and recv() tell to following:
>>>
>>> EAGAIN or EWOULDBLOCK
>>> The socket is marked non-blocking and the requested operation would
>>> block. POSIX.1-2001 allows either error to be returned for this case,
>>> and does not require these constants to have the same value, so a
>>> portable application should check for both possibilities.
>>>
>>> So I added a check for EWOULDBLOCK after the calls to send() and recv()
>>> and return EAGAIN to the caller.
>>>
>>> The other issues are mentioned in the commit message.
>>>
>>> bye,
>>> Sumit
> 
>> This new version ofthe patch adds EINTR to the list of errors where we
>> return EAGAIN to the caller.
> 
>> bye,
>> Sumit
> 
> Ack.
> 


Pushed to master and 1-1-0

- -- 
Stephen Gallagher
RHCE 804006346421761

Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAkug/fUACgkQeiVVYja6o6NnkgCgnWdpiMuQYDOZ2Z+ygtI39niP
TUUAn0f0ROTPMmUBFDWV8ZUlblUNe8mg
=GNJA
-----END PGP SIGNATURE-----



More information about the sssd-devel mailing list