Comment 63 for bug 1573062

------- Comment From <email address hidden> 2016-07-01 02:36 EDT-------
What is the criteria for forward progress of the stress?

I did a quick check for what processes are OOM'd

In new kernel

2 apport
1 cron
1 dhclient
1 gmain
2 in:imklog
1 (journald)
1 kworker/u160:4
1 rs:main
1 stress-ng
972 stress-ng-bighe
157 stress-ng-brk
10 swapper/1
2 swapper/16
17 swapper/2
39 swapper/40
15 swapper/41
1 swapper/65
3 systemd
3 systemd-cgroups
10 systemd-journal
1 systemd-logind

In the 14.04 kernel

1 dhclient
1 in:imklog
1 in:imuxsock
3 irqbalance
1 jbd2/sda2-8
1 kworker/u160:1
1 stress-ng
226 stress-ng-brk
32 swapper/16
3 swapper/23
2 swapper/31
3 swapper/32
22 swapper/46
5 swapper/55
33 swapper/56
3 swapper/63
6 swapper/64
18 swapper/7
6 swapper/72
7 swapper/8

We changed the OOM killer in 4.6 (see https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=aac453635549699c13a84ea1456d5b0e574ef855). Looks like we have good behaviour with 4.6 which could be a result of the change. I am yet to look at the source of memstress_ng, but if the
processes selected for OOM impact the result of the test, we could have a probable explanation. It will also be interesting to continue the bisect and see where we end up.