Bug 2178069

Summary: rfc3315.c:344:7: warning[deadcode.DeadStores]: Value stored to 'outmsgtype' is never read
Product: [Fedora] Fedora Reporter: Petr Menšík <pemensik>
Component: dnsmasqAssignee: Petr Menšík <pemensik>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 39CC: aegorenkov.91, dns-sig, dougsland, pemensik
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-11-27 21:08:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Petr Menšík 2023-03-14 11:10:09 UTC
Description of problem:
Reported by coverity scan of RHEL8 package.

1. dnsmasq-2.79/src/rfc3315.c:344:7: warning[deadcode.DeadStores]: Value stored to 'outmsgtype' is never read
#   342|       
#   343|       {  
#   344|->       outmsgtype = DHCP6REPLY;
#   345|         o1 = new_opt6(OPTION6_STATUS_CODE);
#   346|         put_opt6_short(DHCP6USEMULTI);


Similar version is still on line 351 in latest upstream release.

Version-Release number of selected component (if applicable):
dnsmasq-2.89-1.fc39

How reproducible:
reliable

Steps to Reproduce:
1. run coverity scan on dnsmasq
2.
3.

Actual results:
1. Defect type: CLANG_WARNING
1. dnsmasq-2.79/src/rfc3315.c:344:7: warning[deadcode.DeadStores]: Value stored to 'outmsgtype' is never read
#   342|       
#   343|       {  
#   344|->       outmsgtype = DHCP6REPLY;
#   345|         o1 = new_opt6(OPTION6_STATUS_CODE);
#   346|         put_opt6_short(DHCP6USEMULTI);


Expected results:
Nothing reported

Additional info:

Comment 1 Petr Menšík 2023-03-14 11:53:36 UTC
Reported upstream with candidate patch:

https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2023q1/016930.html

Comment 2 Petr Menšík 2023-03-16 10:54:22 UTC
Fixed by upstream a bit different way:
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=00be8b39e240934e404533deda08cbae2aae25a8

Comment 3 Fedora Release Engineering 2023-08-16 08:14:57 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.

Comment 4 Aoife Moloney 2024-11-08 10:49:36 UTC
This message is a reminder that Fedora Linux 39 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 39 on 2024-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '39'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 39 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 5 Aoife Moloney 2024-11-27 21:08:53 UTC
Fedora Linux 39 entered end-of-life (EOL) status on 2024-11-26.

Fedora Linux 39 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.