Bug 590581 - PATCH: libiscsi get_firmware_foo does not work without first creating a libiscsi context
PATCH: libiscsi get_firmware_foo does not work without first creating a libis...
Status: CLOSED CURRENTRELEASE
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: iscsi-initiator-utils (Show other bugs)
5.5
All Linux
low Severity medium
: rc
: ---
Assigned To: Mike Christie
Red Hat Kernel QE team
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-10 04:40 EDT by Hans de Goede
Modified: 2012-06-27 06:01 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 590580
Environment:
Last Closed: 2012-06-27 06:01:51 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Hans de Goede 2010-05-10 04:40:14 EDT
+++ This bug was initially created as a clone of Bug #590580 +++

Created an attachment (id=412756)
PATCH: call sysfs_init from libiscsi_get_firmware_foo

Hi Mike,

The libiscsi_get_firmware_foo functions do not work without first creating a libiscsi context, while they are intended to work without a context. The problem is that the sysfs code needs to be initialized before use and it is used by
the fwparam code. This patch fixes this by calling sysfs_init() when
libiscsi_get_firmware_foo is called and sysfs_init was not called yet.

I'll clone this bug for 5.5 as I believe we need it there too.

Thanks & Regards,

Hans

p.s.

I can add this to pkg CVS myself if you want, but I'm not sure if I have commit rights there, only one way to find out I guess :)

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