Potential bad use of null-like value

Bug #1853274 reported by ddylihfq
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
oslo.config
Invalid
Undecided
Unassigned

Bug Description

A recent Coverity scan found a potential issue in cfg.py:line 2662

On line 2642 there is a null_check: Comparing 'group' to a null-like value implies that 'group' might be null-like.
(if group is None and name in self._groups:)

Then on line 2662, accessing a property of null-like value 'group' is noted.
(group_name = group.name if group else None)

Coverity screen shot attached with clearer detail.

Is this a potential issue or a false positive? If so this would be classed as CWE-476: NULL Pointer Dereference.

Tags: coverity
Revision history for this message
ddylihfq (ddylihfq) wrote :
Revision history for this message
ddylihfq (ddylihfq) wrote :

No pickup on this yet?

Revision history for this message
Takashi Kajinami (kajinamit) wrote :

The logic pointed does not look like problems at all to me. To be very honest, checking all results from dumb scan requires effort without much gain and I don't really like the idea of pasting the tool result and asking other people to pay effort to these uncertain results.

Changed in oslo.config:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.