[SSSD] [PATCH] Prevent segfault in failover code

Jakub Hrozek jhrozek at redhat.com
Mon Mar 7 09:58:00 UTC 2011


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

This patch should fix a segfault in failover code introduced by my
recent hostname expiration patch.

I didn't realize that when using SRV records, server->common == NULL is
legal as we don't have the server name resolved yet.

The first hunk in the patch is completely unrelated to the crash. But I
think it is correct, server->common == NULL should never mean that the
server is resolved. Should I split the hunk (at least for stable
branches sake) even if it is one-liner?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAk10rCgACgkQHsardTLnvCV7AwCcD3S6hlJIMnF3xxxtkaON/2Gr
IkQAn0ZFtnsyH+YOBBuM7SmwmfAV+o0P
=V/Kz
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Prevent-segfault-in-failover-code.patch
Type: text/x-patch
Size: 1370 bytes
Desc: not available
URL: <https://lists.fedorahosted.org/pipermail/sssd-devel/attachments/20110307/af0290c3/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Prevent-segfault-in-failover-code.patch.sig
Type: application/pgp-signature
Size: 72 bytes
Desc: not available
URL: <https://lists.fedorahosted.org/pipermail/sssd-devel/attachments/20110307/af0290c3/attachment.sig>


More information about the sssd-devel mailing list