Bug 589860 - lsscsi can return (null) instead of module name
Summary: lsscsi can return (null) instead of module name
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: lsscsi
Version: 6.0
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Dan Horák
QA Contact: BaseOS QE - Apps
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-07 06:39 UTC by Dan Horák
Modified: 2010-11-15 14:30 UTC (History)
2 users (show)

Fixed In Version: lsscsi-0.23-2.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-11-15 14:30:43 UTC
Target Upstream Version:

Attachments (Terms of Use)
understand both "NULLs" (1.44 KB, patch)
2010-05-07 06:39 UTC, Dan Horák
no flags Details | Diff

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

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.

Note You need to log in before you can comment on or make changes to this bug.