Re: [SSSD] [PATCH] Prevent segfault in failover code
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 03/07/2011 09:34 AM, Sumit Bose wrote:
On Mon, Mar 07, 2011 at 10:58:00AM +0100, Jakub Hrozek wrote:
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?
> 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/
iEYEARECAAYFAk10+eMACgkQeiVVYja6o6N+iwCdE7HRSc4ebREVtb0q0z7geoM4
GecAoJC6Zx92AfG7VAJqAiDeIeooMfz9
=fl7o
-----END PGP SIGNATURE-----