Bug 49911
Summary: | bash 2.04 has runaway process bug | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Alex Stewart <alex> |
Component: | bash | Assignee: | Tim Waugh <twaugh> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Aaron Brown <abrown> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://www.foogod.com/autonet/ | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-09-26 01:55:11 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Alex Stewart
2001-07-25 01:00:53 UTC
I have put updated bash RPMs up on http://www.foogod.com/software/autonet. These include all of the fixes from the 2.04 RPM, so they should be good for general distribution unless there are any known issues in 2.05 that weren't in 2.04. (someone might want to check whether the "exclude" patch is still needed if anybody knows how to create a test case. The bash code has been changing in this area, so it may no longer be needed. I have included it in the 2.05 RPM just to be safe.) -alex (err.. I meant "export" patch.. sigh.) 2.05 has been in rawhide for about 3 months. Ok, I missed the RPMs in the rawhide FTP directory before, however: RAWHIDE is not an appropriate resolution for this bug. This is not a new feature request, or an issue with some part of the system that nobody uses, this is a confirmed BUG in one of the core components of the system, a potentially sytem crashing bug if it happens to hit the wrong process at the wrong time (which it could do randomly). I have encountered at least one other incident with a runaway system script which I believe may be due to this bug (I was unable to obtain enough info at the time to be sure, but it was similar). Howabout an errata or _something_ to let people know that this problem exists BEFORE it screws over their production systems without warning? (and that there's a fix available). |