../src/db/sysdb_selinux.c: In function 'sysdb_store_selinux_entity': ../src/db/sysdb_selinux.c:106:13: warning: 'dn' may be used uninitialized in this function [-Wmaybe-uninitialized] ../src/db/sysdb_selinux.c:132:20: note: 'dn' was declared here ../src/db/sysdb_selinux.c:92:9: warning: 'objectclass' may be used uninitialized in this function [-Wmaybe-uninitialized] ../src/db/sysdb_selinux.c:129:17: note: 'objectclass' was declared here ../src/providers/ldap/sdap_async_connection.c: In function 'sdap_cli_resolve_done': ../src/providers/ldap/sdap_async_connection.c:1330:8: warning: 'use_tls' may be used uninitialized in this function [-Wmaybe-uninitialized] ../src/providers/ldap/sdap_async_connection.c:1303:11: note: 'use_tls' was declared here ../src/providers/ldap/sdap_sudo.c: In function 'sdap_sudo_load_sudoers_done': ../src/providers/ldap/sdap_sudo.c:755:9: warning: 'rules_count' may be used uninitialized in this function [-Wmaybe-uninitialized] ../src/providers/ldap/sdap_sudo.c:608:12: note: 'rules_count' was declared here ../src/providers/krb5/krb5_utils.c: In function 'get_cc_be_ops': ../src/providers/krb5/krb5_utils.c:588:5: warning: 'be' may be used uninitialized in this function [-Wmaybe-uninitialized] ../src/providers/krb5/krb5_utils.c:567:28: note: 'be' was declared here In file included from ../src/providers/krb5/krb5_child_handler.c:25:0: ../src/providers/krb5/krb5_child_handler.c: In function 'handle_child_send': ../src/util/util.h:280:11: warning: 'username_len' may be used uninitialized in this function [-Wmaybe-uninitialized] ../src/providers/krb5/krb5_child_handler.c:95:12: note: 'username_len' was declared here ../src/sss_client/pam_sss.c: In function 'pam_sss': ../src/sss_client/pam_sss.c:1265:9: warning: 'services' may be used uninitialized in this function [-Wmaybe-uninitialized] ../src/sss_client/pam_sss.c:1089:11: note: 'services' was declared here ../src/providers/krb5/krb5_utils.c: In function 'get_cc_be_ops': ../src/providers/krb5/krb5_utils.c:588:5: warning: 'be' may be used uninitialized in this function [-Wmaybe-uninitialized] ../src/providers/krb5/krb5_utils.c:567:28: note: 'be' was declared here ../src/providers/ipa/ipa_session.c: In function 'ipa_session_handler_done': ../src/providers/ipa/ipa_session.c:128:13: warning: 'map_count' may be used uninitialized in this function [-Wmaybe-uninitialized] ../src/providers/ipa/ipa_session.c:128:13: warning: 'maps' may be used uninitialized in this function [-Wmaybe-uninitialized] ../src/providers/ipa/ipa_session.c:121:13: warning: 'default_user' may be used uninitialized in this function [-Wmaybe-uninitialized] ../src/providers/ipa/ipa_session.c:121:13: warning: 'map_order' may be used uninitialized in this function [-Wmaybe-uninitialized] ../src/responder/nss/nsssrv_services.c: In function ‘setservent_step_done’: ../src/responder/nss/nsssrv_services.c:1497:60: warning: ‘res’ may be used uninitialized in this function [-Wmaybe-uninitialized] ../src/responder/pam/pamsrv_cmd.c: In function ‘pam_reply’: ../src/responder/pam/pamsrv_cmd.c:589:13: warning: ‘len’ may be used uninitialized in this function [-Wmaybe-uninitialized]
I've fixed
../src/sss_client/pam_sss.c:1265:9: warning: 'services' may be used uninitialized in this function [-Wmaybe-uninitialized]
in patch 42ea38d7d06673bf6dc16ccfbd19e27f0a696b28 because it was causing SIGABRT in many cases.
The others still need to be addressed.
Fields changed
keywords: => easyfix
milestone: NEEDS_TRIAGE => SSSD 1.9.0 beta 5 rhbz: => 0
owner: somebody => nguay
master: 8bbf89c5ab798c112773fe23515c3a9df56dde71
milestone: SSSD 1.9.0 beta 6 => SSSD 1.9.0 beta 5 patch: 0 => 1 resolution: => fixed status: new => closed
Metadata Update from @sgallagh: - Issue assigned to nguay - Issue set to the milestone: SSSD 1.9.0 beta 5
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/2421
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.