Bug 701890

Summary:	misprocessing of invalid PID argument for ksh built-in kill
Product:	Red Hat Enterprise Linux 6	Reporter:	Michal Hlavinka <mhlavink>
Component:	ksh	Assignee:	Michal Hlavinka <mhlavink>
Status:	CLOSED ERRATA	QA Contact:	qe-baseos-tools-bugs
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.0	CC:	mfranc, ovasik, prc
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	691850	Environment:
Last Closed:	2011-12-06 16:18:45 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Michal Hlavinka 2011-05-04 08:16:46 UTC

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

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.

--- Additional comment from mhlavink on 2011-05-04 04:12:19 EDT ---

reproducible

--- Additional comment from mhlavink on 2011-05-04 04:15:26 EDT ---

Created attachment 496723 [details]
patch to fix this

Comment 3 Michal Hlavinka 2011-08-12 08:51:53 UTC

when checking test plan for ksh, I've found a regression:

this fix caused ksh regression:
$ ksh -c 'kill %'
Segmentation fault (core dumped)

Comment 4 Michal Hlavinka 2011-08-12 09:22:04 UTC

ok, this regression does not happen with ksh version we have in RHEL-6

Comment 6 errata-xmlrpc 2011-12-06 16:18:45 UTC

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-2011-1647.html