Bug 961648

Summary: user(s) processes are not moved into the group at login time + cgred restart segfault
Product: Red Hat Enterprise Linux 6 Reporter: lejeczek <peljasz>
Component: libcgroupAssignee: Peter Schiffer <pschiffe>
Status: CLOSED DUPLICATE QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.4CC: jsafrane, ovasik, varekova
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-05-17 15:48:48 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:

Description lejeczek 2013-05-10 07:37:32 UTC 
Description of problem:

it seems cgred service starts at boot but each subsequent restart results in segfault
also, more! importantly processes initiated by a user declared in rules are not being acted upon when user logins in

Version-Release number of selected component (if applicable):

libcgroup-0.37-7.el6.x86_64
pam-1.1.1-13.el6.x86_64
2.6.32-358.2.1.el6.x86_64

How reproducible:

mount {
  cpu = /cgroup/cpu;
  cpuset  = /cgroup/cpuset;
  cpuacct = /cgroup/cpuacct;
  memory  = /cgroup/memory;
  devices = /cgroup/devices;
  freezer = /cgroup/freezer;
  net_cls = /cgroup/net_cls;
  blkio = /cgroup/blkio;
}

group . {
  perm {
    task {
      uid = root;
      gid = root;
    }
    admin {
      uid = root;
      gid = root;
    }
  }
}

group limit {
  memory {
    memory.limit_in_bytes = 15G;
  }
  cpuset {
    cpuset.cpus = "5";
    cpuset.mems = 0;
  }
}

and

aUser memory,cpuset  limit/


Steps to Reproduce:
1.
2.
3.
  
Actual results:

declared users are not confined/controlled

Expected results:

when user logs in all processes should be move into the cgroup


Additional info:
Comment 2 Ondrej Vasik 2013-05-17 15:48:48 UTC 

*** This bug has been marked as a duplicate of bug 961646 ***