From: Michal Hocko <mhocko@kernel.org>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: Dave Chinner <david@fromorbit.com>,
xfs@oss.sgi.com, linux-xfs@vger.kernel.org, linux-mm@kvack.org
Subject: Re: Excessive xfs_inode allocations trigger OOM killer
Date: Mon, 3 Oct 2016 19:54:09 +0200 [thread overview]
Message-ID: <20161003175407.GA26788@dhcp22.suse.cz> (raw)
In-Reply-To: <878tu5xrmx.fsf@mid.deneb.enyo.de>
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
next prev parent reply other threads:[~2016-10-03 17:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 19:48 Excessive xfs_inode allocations trigger OOM killer Florian Weimer
2016-09-20 20:30 ` Dave Chinner
2016-09-20 20:56 ` Florian Weimer
2016-09-20 21:46 ` Dave Chinner
2016-09-21 5:45 ` Florian Weimer
2016-09-21 8:04 ` Michal Hocko
2016-09-21 8:06 ` Michal Hocko
2016-09-26 17:33 ` Florian Weimer
2016-09-26 20:02 ` Michal Hocko
2016-10-03 17:35 ` Florian Weimer
2016-10-03 17:54 ` Michal Hocko [this message]
2016-09-20 21:51 ` Christoph Hellwig
2016-09-20 21:54 ` Florian Weimer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161003175407.GA26788@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=david@fromorbit.com \
--cc=fw@deneb.enyo.de \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).