From: Florian Weimer <fw@deneb.enyo.de>
To: linux-xfs@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org
Subject: xfs_inode not reclaimed/memory leak on 5.2.16
Date: Mon, 30 Sep 2019 09:28:27 +0200 [thread overview]
Message-ID: <87pnji8cpw.fsf@mid.deneb.enyo.de> (raw)
Simply running “du -hc” on a large directory tree causes du to be
killed because of kernel paging request failure in the XFS code.
I ran slabtop, and it showed tons of xfs_inode objects.
The system was rather unhappy after that, so I wasn't able to capture
much more information.
Is this a known issue on Linux 5.2? I don't see it with kernel
5.0.20. Those are plain upstream kernels built for x86-64, with no
unusual config options (that I know of).
next reply other threads:[~2019-09-30 7:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-30 7:28 Florian Weimer [this message]
2019-09-30 8:54 ` xfs_inode not reclaimed/memory leak on 5.2.16 Dave Chinner
2019-09-30 19:07 ` Florian Weimer
2019-09-30 21:17 ` [bug, 5.2.16] kswapd/compaction null pointer crash [was Re: xfs_inode not reclaimed/memory leak on 5.2.16] Dave Chinner
2019-09-30 21:42 ` Florian Weimer
2019-10-01 9:10 ` Vlastimil Babka
2019-10-01 19:40 ` Florian Weimer
2019-10-07 13:28 ` Vlastimil Babka
2019-10-07 13:56 ` Vlastimil Babka
2019-10-08 8:52 ` Mel Gorman
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=87pnji8cpw.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
/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