Bug 174586 - RHEL4: killall crashes on long variable name
Summary: RHEL4: killall crashes on long variable name
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: psmisc
Version: 4.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Karel Zak
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 187538
TreeView+ depends on / blocked
 
Reported: 2005-11-30 14:37 UTC by Bastien Nocera
Modified: 2007-11-30 22:07 UTC (History)
1 user (show)

Fixed In Version: RHBA-2006-0363
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-05-17 19:19:40 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2006:0363 0 normal SHIPPED_LIVE psmisc bug fix update 2006-05-17 04:00:00 UTC

Description Bastien Nocera 2005-11-30 14:37:55 UTC
Same patch as RHEL3 should apply.

+++ This bug was initially created as a clone of Bug #174585 +++

In /proc/<PID>/stat, the second column contains the short process name in
between brackets. For example:
14734 (gnome-pty-helpe) S 14733 2917 2917 0 -1 8388608 210 0 0 0 0 0 0 0 17 0 1
0 2854587 2224128 153 4294967295 134512640 134520764 3214533232 0 582 0 0
805310466 16385 0 0 0 17 0 0 0

killall parses that second column using this fscanf pattern:
-      okay = fscanf (file, "%*d (%[^)]", comm) == 1;
As comm is only 16 chars long, killall will crash if a kernel module sets its
own name to be longer than that. Patch from sprabhu attached

-- Additional comment from bnocera on 2005-11-30 09:36 EST --
Created an attachment (id=121634)
psmisc-21.3-comm_16chars.patch

Comment 7 Red Hat Bugzilla 2006-05-17 19:19:42 UTC
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.

http://rhn.redhat.com/errata/RHBA-2006-0363.html



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