Bug 589860 - lsscsi can return (null) instead of module name
lsscsi can return (null) instead of module name
Status: CLOSED CURRENTRELEASE
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: lsscsi (Show other bugs)
6.0
All Linux
low Severity medium
: rc
: ---
Assigned To: Dan Horák
BaseOS QE - Apps
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-07 02:39 EDT by Dan Horák
Modified: 2010-11-15 09:30 EST (History)
2 users (show)

See Also:
Fixed In Version: lsscsi-0.23-2.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-11-15 09:30:43 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


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

  None (edit)
Description Dan Horák 2010-05-07 02:39:24 EDT
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 Product and Program Management 2010-05-07 02:40:42 EDT
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 09:30:43 EST
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.