SSSD / sssd

Clone

#1864 Bad comparisons in checks found by new Coverity instance
Closed: Fixed None Opened 11 years ago by jhrozek.

Closed: Fixed
Reopen Issue

The new Coverity instance found several cases where we check for a different variable name after allocation or a different operation, such as here:

385                rdomain = talloc_strdup(tmp_ctx, default_domain);
386                if (default_domain == NULL) {
387                    DEBUG(SSSDBG_OP_FAILURE, ("talloc_strdup failed.\n"));
388                    ret = ENOMEM;
389                    goto done;
390                }

This ticket tracks all there problems.

Fields changed

coverity: 10021 => 10021, 10020,10014

Fields changed

coverity: 10021, 10020,10014 => 10021, 10020,10014,10013

Fields changed

owner: somebody => jhrozek
patch: 0 => 1
status: new => assigned

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.10.0
rhbz: => 0

Fields changed

milestone: SSSD 1.10.0 => SSSD 1.10 beta

resolution: => fixed
status: assigned => closed

Additional fix: 4d09e8a

Metadata Update from @jhrozek:
- Issue assigned to jhrozek
- Issue set to the milestone: SSSD 1.10 beta
7 years ago

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/2906

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata
None
None
None
major
defect
SSSD
1.9.4
None
0
1
0
0
0
None
None
10021, 10020,10014,10013
None
None
None
None
None
None
None
Powered by Pagure 5.13.3
Documentation • File an Issue • About • SSH Hostkey/Fingerprint
© Red Hat, Inc. and others.