Bug 846401

Summary: Processes in RHEL 5 are started on a processor not defined in their Cpuset
Product: Red Hat Enterprise Linux 5 Reporter: Christian Huffman <chuffman>
Component: kernelAssignee: Jacob Tanenbaum <jtanenba>
Status: CLOSED WORKSFORME QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: high Docs Contact:
Priority: high    
Version: 5.5CC: dhoward, mflitter
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-03-17 17:18:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 743405    
Attachments:
Description Flags
Result of /proc/<pid>/status on RHEL5.
none
Result of /proc/<pid>/status on RHEL6.
none
Cpuset on RHEL5 none

Description Christian Huffman 2012-08-07 16:54:06 UTC
Description of problem:
In RHEL 5 processes are added to the appropriate cpuset when created, but are running on a CPU not allowed by that cpuset.

When tested on RHEL 6 all processes are 

Version-Release number of selected component (if applicable):
kernel 2.6.18-194.32.1.el5
RHEL 5.5

How reproducible:
Not certain if this is every process, or only on certain ones.  It has been noticed to occur on java threads.

Steps to Reproduce:
1. Define a cpuset with parameters seen in attached 'cpuset.tar' on the version indicated above.
2. Start a task for use with this cpuset, and examine the current running processor.
  
Actual results:
Task is started with processor 0 instead of one in the defined set.

Expected results:
Task is started with a processor in the same cpuset.

Additional info:
This works as expected in RHEL 6 when using the cpuset filesystem (and not cgroups).

Attaching the cpuset from RHEL 5, and the /proc/<PID>/status from a process running in both RHEL 5 and RHEL 6.

Comment 1 Christian Huffman 2012-08-07 16:55:24 UTC
Created attachment 602800 [details]
Result of /proc/<pid>/status on RHEL5.

Result of /proc/<pid>/status on RHEL5.

Comment 2 Christian Huffman 2012-08-07 16:55:42 UTC
Created attachment 602801 [details]
Result of /proc/<pid>/status on RHEL6.

Result of /proc/<pid>/status on RHEL6.

Comment 3 Christian Huffman 2012-08-07 16:56:03 UTC
Created attachment 602802 [details]
Cpuset on RHEL5

Cpuset on RHEL5

Comment 4 RHEL Program Management 2012-10-30 06:04:48 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 5 RHEL Program Management 2013-07-24 04:14:26 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 7 Jacob Tanenbaum 2014-03-17 17:18:49 UTC
Could not reproduce the error mentioned. It is attached to a closed customer issue.