Bug 699589

RHEL6 does not have the code that this BZ refers to or that the patch modifies.  I cant seem to get the system to hang up like is described here, can you???

Larry Woodman

Yes, we did reproduce this hung in RHEL6 before, and tested a little bit upstream but found some more patches are needed to fix another oom issue, 

http://marc.info/?l=linux-kernel&m=130587844107425&w=2

Currently, we are waiting for oom refresh went into RHEL6.2 for re-validation of this problem.

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.

It been a long time since this BZ was opened and LOTS of upstream mm patches have been backported to RHEL6.  Can someone see if this is still a problem with RHEL6.5???

Larry Woodman

(In reply to Larry Woodman from comment #10)
> It been a long time since this BZ was opened and LOTS of upstream mm patches
> have been backported to RHEL6.  Can someone see if this is still a problem
> with RHEL6.5???
> 
> Larry Woodman

Yes, Larry. QE will check it with RHEL6.5 and see if this is still a problem.

Thanks,
Chun

Created attachment 854811 [details]
testing log on RHEL-6.5

(In reply to Larry Woodman from comment #10)
> It been a long time since this BZ was opened and LOTS of upstream mm patches
> have been backported to RHEL6.  Can someone see if this is still a problem
> with RHEL6.5???
> 
> Larry Woodman

testing on RHEL-6.5 kernel 2.6.32-431.el6.x86_64, System memory was exhausted and OOM was triggered. its seems the issue is not existing on RHEL-6.5 any more.

more testing log as the attachments.
---snip---
[ 7744]     0  7744    33567      131   7       0             0 python 
[ 7745]     0  7745    33567      130   4       0             0 python 
[ 7746]     0  7746    33567      130   7       0             0 python 
[ 7747]     0  7747    33567      132   0       0             0 python 
[ 7748]     0  7748    33567      132   4       0             0 python 
[ 7749]     0  7749    33567      130   4       0             0 python 
[ 7750]     0  7750    33567      130   5       0             0 python 
[ 7751]     0  7751    33567      132   3       0             0 python 
[ 7752]     0  7752    33567      130   1       0             0 python 
[ 7753]     0  7753    33567      116   6       0             0 python 
[ 7754]     0  7754    33567      119   3       0             0 python 
Out of memory: Kill process 1480 (rsyslogd) score 1 or sacrifice child 
Killed process 1480, UID 0, (rsyslogd) total-vm:249088kB, anon-rss:76kB, file-rss:24kB 
rs:main Q:Reg invoked oom-killer: gfp_mask=0xd0, order=0, oom_adj=0, oom_score_adj=0 
rs:main Q:Reg cpuset=/ mems_allowed=0 
Pid: 1481, comm: rs:main Q:Reg Not tainted 2.6.32-431.el6.x86_64 #1 
Call Trace: 
 [<ffffffff810d05b1>] ? cpuset_print_task_mems_allowed+0x91/0xb0 
 [<ffffffff81122960>] ? dump_header+0x90/0x1b0 
 [<ffffffff8122798c>] ? security_real_capable_noaudit+0x3c/0x70 
 [<ffffffff81122de2>] ? oom_kill_process+0x82/0x2a0 
 [<ffffffff81122d21>] ? select_bad_process+0xe1/0x120 
 [<ffffffff81123220>] ? out_of_memory+0x220/0x3c0 
 [<ffffffff8112fb3c>] ? __alloc_pages_nodemask+0x8ac/0x8d0 
 [<ffffffff8116e482>] ? kmem_getpages+0x62/0x170 
 [<ffffffff8116f09a>] ? fallback_alloc+0x1ba/0x270 
 [<ffffffff8116eaef>] ? cache_grow+0x2cf/0x320 
 [<ffffffff8116ee19>] ? ____cache_alloc_node+0x99/0x160 
 [<ffffffff8116fd9b>] ? kmem_cache_alloc+0x11b/0x190 
 [<ffffffff810efcf5>] ? taskstats_exit+0x305/0x390 
 [<ffffffff81076f17>] ? do_exit+0x157/0x870 
 [<ffffffff81077688>] ? do_group_exit+0x58/0xd0 
 [<ffffffff8108d046>] ? get_signal_to_deliver+0x1f6/0x460 
 [<ffffffff8100a265>] ? do_signal+0x75/0x800 
 [<ffffffff8118e7b4>] ? cp_new_stat+0xe4/0x100 
 [<ffffffff812334eb>] ? selinux_file_permission+0xfb/0x150 
 [<ffffffff810b1c0b>] ? sys_futex+0x7b/0x170 
 [<ffffffff8100aa80>] ? do_notify_resume+0x90/0xc0 
 [<ffffffff8100b341>] ? int_signal+0x12/0x17

(In reply to Li Wang from comment #13)
> (In reply to Larry Woodman from comment #10)
> > It been a long time since this BZ was opened and LOTS of upstream mm patches
> > have been backported to RHEL6.  Can someone see if this is still a problem
> > with RHEL6.5???
> > 
> > Larry Woodman
> 
> testing on RHEL-6.5 kernel 2.6.32-431.el6.x86_64, System memory was
> exhausted and OOM was triggered. its seems the issue is not existing on
> RHEL-6.5 any more.
> 
> more testing log as the attachments.
> ---snip---
> [ 7744]     0  7744    33567      131   7       0             0 python 
> [ 7745]     0  7745    33567      130   4       0             0 python 
[...]

but I found that the OOM was not killing riht task, the problem like this:
https://bugzilla.redhat.com/show_bug.cgi?id=822790
it should be pay attention to the new OOM problem.

*nod* Since bug 822790 addresses some of the OOM killing the
wrong tasks.. closing this issue per comment#13.