Bug 1026820 - fix coverity warnings
Summary: fix coverity warnings
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libiscsi
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Paolo Bonzini
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-05 13:48 UTC by Paolo Bonzini
Modified: 2014-06-18 04:49 UTC (History)
7 users (show)

Fixed In Version: libiscsi-1.9.0-3.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 11:41:57 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Paolo Bonzini 2013-11-05 13:48:42 UTC 
Coverity scan of libiscsi reveals few defects.  Some of them are just cosmetic, and others would only apply to malicious targets, but the number is small enough that it's worth fixing them.

http://cov01.lab.eng.brq.redhat.com/covscanhub/task/6128/log/libiscsi-1.9.0-2.el7/run1/results.html
Comment 1 Miroslav Rezanina 2013-11-07 14:23:58 UTC 
Committed in libiscsi-1.9.0-3.el7
Comment 3 langfang 2014-02-26 10:24:17 UTC 
Hi,Paolo

  Could you can provide a method to verify this bug ?

thanks 
fang lang
Comment 4 Paolo Bonzini 2014-02-26 10:55:42 UTC 
Just regular functional testing is enough.

You can check the old results:

http://cov01.lab.eng.brq.redhat.com/covscanhub/task/6128/log/libiscsi-1.9.0-2.el7/run1/results.html

against the new ones:

http://cov01.lab.eng.brq.redhat.com/covscanhub/task/9572/log/libiscsi-1.9.0-6.el7/run1/results.html
Comment 5 juzhang 2014-03-03 07:06:02 UTC 
KVM QE ran several features(migration, virtual block) functional testing basked on libiscsi by using libiscsi-1.9.0-6.el7.
Comment 7 Ludek Smid 2014-06-13 11:41:57 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.
Note You need to log in before you can comment on or make changes to this bug.