Bug 89038
Summary: | ptrace calls broken in security update kernel-2.4.18-27.7 | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Chris Gottbrath <chrisg> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 7.1 | CC: | abraxis, blake, jaroslaw.polok |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
URL: | http://www.ussg.iu.edu/hypermail/linux/kernel/0304.0/0137.html | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-09-30 15:40:48 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
Chris Gottbrath
2003-04-16 19:50:00 UTC
Actually I should have said as reported "in the thread" http://www.ussg.iu.edu/hypermail/linux/kernel/0304.0/0137.html the post that is most relevant to our specific problems with this patch is http://www.ussg.iu.edu/hypermail/linux/kernel/0304.0/0601.html From the users perspective trying to use TotalView on any target results in TotalView getting quite violently killed by the kernel when the kernel oopses trying to fufill a ptrace call. It is not obvious to users that the problem is a kernel bug as opposed to a TotalView bug. Thanks, Chris The secruity update kernel being shipped to address the ptrace exploit is faulty. It causes a kernel oops whenever doing a ptrace call on a zombie process. While the effect is quite clear in the Etnus TotalView debugger causing the debugger to crash, the problem ought to be a concern to all users. It also causes a stability problem on heavilly loaded machines as documented here: http://www.ussg.iu.edu/hypermail/linux/kernel/0304.0/0137.html This ought to be of particular interest to RedHat who wants to provide a stable and secure platform for all users! The fix is simple, safe, and correct. When should we plan to see a kernel update for the affected RPM kernel packages? For easy testing, you may download TotalView and a trial license from http://www.etnus.com to observe the severity of the problem. Etnus has had several users report this problem so this a particularly urgent issue in our opinion. HELLOOOOOOOOOOOO! This is a simple one. Is anyone listening? I'm also having problems with kernel-2.4.20-13.7 on RHL7.3. I've been trying to get a core dump out of squid for a while so I can send stacktraces to the squid developers without success. gdb also wouldn't allow me to do a backtrace when running squid under gdb. I have reverted the two ptrace patches in 2.4.20-13.7 and everything works properly now. Of couse, I'm going to have to put them back when I am finished debugging the squid problem. This is extremely inconvenient on a production box. Fixes are available for 8.0 and 9 at least, see bug 89057, not sure about 7.x. Seems to be fixed for 7.X in the 2.4.20-18.7 kernel update as well ... Thanks for the bug report. However, Red Hat no longer maintains this version of the product. Please upgrade to the latest version and open a new bug if the problem persists. The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, and if you believe this bug is interesting to them, please report the problem in the bug tracker at: http://bugzilla.fedora.us/ |