Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 152866

Summary: lsraid/raidtools fails segmentation violation after 100+days uptime
Product: [Retired] Fedora Legacy Reporter: David Lawrence <dkl>
Component: GeneralAssignee: Fedora Legacy Bugs <bugs>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: pekkas
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description David Lawrence 2005-03-30 23:30:13 UTC
RH 9.0: /sbin/lsraid -A -p violates due to increasing line length in
/proc/partitions. Compiled line length is 100. in 'load_partitions()', opens
/proc/partitions and reads up to MAX_LINE_LENGTH. Since line lengths in
/proc/partitions can exceed 100 chs, susequent reads get rubbish read and result
is violation. Increasing MAX_LINE_LENGTH to 255 avoided problem and 
stopped violation. (This was the version of raidtools downloaded from 

I note that FC3 does not have as many columns in /proc/partitions and so would not
suffer from this problem

------- Additional Comments From 2004-12-21 08:29:13 ----

While this would be an easily fixable bug, this is not a security problem as
those tools are not setuid.  Feel free to reopen and debate this again if at
some point we'll have to make a RHL9 update to raidtools for some other reason.

------- Bug moved to this database by 2005-03-30 18:30 -------

This bug previously known as bug 2332 at
Originally filed under the Fedora Legacy product and General component.

Unknown priority P2. Setting to default priority "normal".
Unknown platform PC. Setting to default platform "All".
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here,
   Previous reporter was
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.