Bug 160882 - i2o RAID monitoring memory leak
i2o RAID monitoring memory leak
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Tom Coughlan
Brian Brock
Depends On:
Blocks: 156322
  Show dependency treegraph
Reported: 2005-06-17 19:10 EDT by Warren Togami
Modified: 2007-11-30 17:07 EST (History)
5 users (show)

See Also:
Fixed In Version: RHSA-2005-514
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-10-05 09:32:46 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
patch against kernel-2.6.9-11.14.EL (6.15 KB, patch)
2005-06-17 19:10 EDT, Warren Togami
no flags Details | Diff
Fixed duplicated sg_list_cleanup (6.26 KB, patch)
2005-06-20 11:09 EDT, Markus Lidel
no flags Details | Diff

  None (edit)
Description Warren Togami 2005-06-17 19:10:33 EDT
Markus Lidel (upstream I2O driver maintainer) said that coughlan@redhat.com
discovered a serious memory leak in the i2o_config driver, where if you
constantly monitor your RAID arrays using I2O raidutils, you will OOM and kill
your system.

Markus provided the attached patch against kernel-2.6.9-11.14.EL.  I personally
wont have a chance to test this patch until I am back home on June 28th.

Apparently this is part of a larger batch of I2O bug fixes currently in akpm's tree.
Comment 1 Warren Togami 2005-06-17 19:10:33 EDT
Created attachment 115645 [details]
patch against kernel-2.6.9-11.14.EL
Comment 2 Hiro Yoshioka 2005-06-20 08:21:24 EDT
the patch has duplicate label `sg_list_cleanup'. could you clean up?
Comment 3 Markus Lidel 2005-06-20 11:09:03 EDT
Created attachment 115691 [details]
Fixed duplicated sg_list_cleanup
Comment 12 Red Hat Bugzilla 2005-10-05 09:32:46 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. 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.