Bug 691850 – misprocessing of invalid PID argument for ksh built-in kill

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 691850 - misprocessing of invalid PID argument for ksh built-in kill

Summary:	misprocessing of invalid PID argument for ksh built-in kill

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 5
Classification:	Red Hat
Component:	ksh (Show other bugs)
Sub Component:
Version:	5.4
Hardware:	Unspecified Linux

Priority	unspecified Severity medium
Target Milestone:	rc
Target Release:	---
Assigned To:	Michal Hlavinka
QA Contact:	qe-baseos-tools
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2011-03-29 12:27 EDT by Kevin Logan
Modified:	2013-11-12 09:02 EST (History)
CC List:	4 users (show)

See Also:
Fixed In Version:	ksh-20100621-1.el5
Doc Type:	Bug Fix
Doc Text:	kill builtin did not handle extra large numbers and just reported -1 internally. This value was interpreted as -1 option thus ksh killed all user processes. This updated version has improved handling of pid conversion errors. When too big number is used, it reports error correctly.
Story Points:	---
Clone Of:
Clones:	701890 (view as bug list)
Environment:
Last Closed:	2012-02-21 00:50:41 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
patch to fix this (1.55 KB, patch) 2011-05-04 04:15 EDT, Michal Hlavinka	no flags	Details \| Diff
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2012:0159	normal	SHIPPED_LIVE	ksh bug fix and enhancement update	2012-02-20 09:53:47 EST

Groups: None (edit)

Description Kevin Logan 2011-03-29 12:27:53 EDT

Description of problem: When the ksh built-in kill is called with a very large, non-existent PID value, it's treated like -1 (kill all processes owned by the user).

Version-Release number of selected component (if applicable): 20080202-14.el5

How reproducible: Every time

Steps to Reproduce:
1.Start a ksh session
2.Run a command like "kill 11269117401228512356"
  
Actual results:  All processes owned by the user are killed, like the -1 argument would normally do.

Expected results: 
error message - "kill: 11269117401228512356: no such process"

Additional info:  We encountered this when a user was trying to kill a series of processes.  The user mis-entered the process list without separating spaces.

Comment 1 Michal Hlavinka 2011-05-04 04:12:19 EDT

reproducible

Comment 2 Michal Hlavinka 2011-05-04 04:15:26 EDT

Created attachment 496723 [details]
patch to fix this

Comment 5 Michal Hlavinka 2012-01-23 09:06:42 EST

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
kill builtin did not handle extra large numbers and just reported -1 internally. This value was interpreted as -1 option thus ksh killed all user processes. This updated version has improved handling of pid conversion errors. When too big number is used, it reports error correctly.

Comment 6 errata-xmlrpc 2012-02-21 00:50:41 EST

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-0159.html

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