Re: Excessive xfs_inode allocations trigger OOM killer

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon 03-10-16 19:35:18, Florian Weimer wrote:
> * Michal Hocko:
> 
> >> I'm not sure if I can reproduce this issue in a sufficiently reliable
> >> way, but I can try.  (I still have not found the process which causes
> >> the xfs_inode allocations go up.)
> >> 
> >> Is linux-next still the tree to test?
> >
> > Yes it contains all the compaction related fixes which we believe to
> > address recent higher order OOMs.
> 
> I tried 4.7.5 instead.  I could not reproduce the issue so far there.
> Thanks to whoever fixed it. :)

The 4.7 stable tree contains a workaround rather than the full fix we
would like to have in 4.9. So if you can then testing the current
linux-next would be really appreciated.

-- 
Michal Hocko
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [XFS Filesystem Development (older mail)]     [Linux Filesystem Development]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux RAID]     [Linux SCSI]


  Powered by Linux