[SSSD] [PATCH] Do not attempt to resolve nameless servers

Stephen Gallagher sgallagh at redhat.com
Fri Apr 1 19:37:40 UTC 2011


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

On 04/01/2011 03:34 PM, Stephen Gallagher wrote:
> On 04/01/2011 07:45 AM, Jakub Hrozek wrote:
>> The attached patch reverts the change I introduced earlier with my patch
>> c825253e74027f87b900c0b811ae019d767c0848.
> 
>> The patch is a one-liner but its context is a little more complex - I
>> actually reached out to Martin Nagy, who wrote much of the original fail
>> over code to be sure.
> 
>> The fail over code is not strictly in charge of resolving. Its main
>> function is to provide a server to connect to for a service.
> 
>> It is legal, although not currently used, to have a server that has no
>> name (server->common == NULL). In this case, no resolving should be done
>> and it is assumed that the failover user, which are the SSSD back ends
>> in our case, would perform any resolving out of band, perhaps using the
>> user_data attribute of fo_server structure.
> 
>> The attached patch would fix the segfault described in #692472 but not
>> its root cause, which appears to be an issue with the confdb.
> 
> 
> Ack.
> 
> 

Pushed to master and sssd-1-5


- -- 
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.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAk2WKYQACgkQeiVVYja6o6Pf3QCfXgctwN60EyBTZLFjcfMJ9nrF
QrUAni5qYo+9WWQWbvH+TRPd3zEpBa9k
=za/x
-----END PGP SIGNATURE-----



More information about the sssd-devel mailing list