Bug 589860

Summary: lsscsi can return (null) instead of module name
Product: Red Hat Enterprise Linux 6 Reporter: Dan Horák <dhorak>
Component: lsscsiAssignee: Dan Horák <dhorak>
Status: CLOSED CURRENTRELEASE QA Contact: BaseOS QE - Apps <qe-baseos-apps>
Severity: medium Docs Contact:
Priority: low    
Version: 6.0CC: mnowak, rvokal
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: lsscsi-0.23-2.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-15 14:30:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
understand both "NULLs" none

Description Dan Horák 2010-05-07 06:39:24 UTC
Created attachment 412245 [details]
understand both "NULLs"

commit 0f4f81dce93774a447da3ceb98cce193ef84a3fa (reported as bug #589613 for RHEL6, already present in Fedora kernels) in kernel changes the string representation of NULL from <NULL> to (null) to be consistent with glibc. This change breaks the handling of the "proc_name" attribute in one_host_handling() and lsscsi is then unable to return module name for a driver. The attached patch changes lsscsi that it understands both "NULLs". Patch is accepted by upstream and will appear in upcoming release.

Comment 1 RHEL Program Management 2010-05-07 06:40:42 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 4 releng-rhel@redhat.com 2010-11-15 14:30:43 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.