On 2017-01-11 Mel Gorman wrote: > On Wed, Jan 11, 2017 at 12:11:46PM +0000, Mel Gorman wrote: > > On Wed, Jan 11, 2017 at 04:32:43AM -0600, Trevor Cordes wrote: > > > Hi! I have biected a nightly oom-killer flood and crash/hang on > > > one of the boxes I admin. It doesn't crash on Fedora 23/24 > > > 4.7.10 kernel but does on any 4.8 Fedora kernel. I did a vanilla > > > bisect and the bug is here: > > > > > > commit b2e18757f2c9d1cdd746a882e9878852fdec9501 > > > Author: Mel Gorman <mgor...@techsingularity.net> > > > Date: Thu Jul 28 15:45:37 2016 -0700 > > > > > > mm, vmscan: begin reclaiming pages on a per-node basis > > > > > > > Michal Hocko recently worked on a bug similar to this. Can you test > > the following patch that is currently queued in Andrew Morton's > > tree? It applies cleanly to 4.9 > > > > I should have pointed out that this patch primarily affects memcg but > the bug report did not include an OOM report and did not describe > whether memcgs could be involved or not. If memcgs are not involved > then please post the first full OOM kill.
I will apply your patch tonight and it will take 48 hours to confirm that it is "good" (<24 hours if it's bad), and I will reply back. I'm not sure how I can tell if my bug is because of memcgs so here is a full first oom example (attached). Thanks for the help!
oom-example
Description: Binary data
