From: Matt Fleming <matt@readmodwrite.com>
To: willy@infradead.org
Cc: adilger.kernel@dilger.ca, akpm@linux-foundation.org,
linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
luka.2016.cs@gmail.com, tytso@mit.edu,
Barry Song <baohua@kernel.org>,
kernel-team@cloudflare.com, Vlastimil Babka <vbabka@suse.cz>,
Miklos Szeredi <miklos@szeredi.hu>,
Amir Goldstein <amir73il@gmail.com>,
Dave Chinner <david@fromorbit.com>,
Qi Zheng <zhengqi.arch@bytedance.com>,
Roman Gushchin <roman.gushchin@linux.dev>,
Muchun Song <muchun.song@linux.dev>
Subject: Re: Potential Linux Crash: WARNING in ext4_dirty_folio in Linux kernel v6.13-rc5
Date: Thu, 3 Apr 2025 13:29:44 +0100 [thread overview]
Message-ID: <CAENh_SSbkoa3srjkAMmJuf-iTFxHOtwESHoXiPAu6bO7MLOkDA@mail.gmail.com> (raw)
In-Reply-To: <20250326105914.3803197-1-matt@readmodwrite.com>
On Wed, Mar 26, 2025 at 10:59 AM Matt Fleming <matt@readmodwrite.com> wrote:
>
> Hi there,
>
> I'm also seeing this PF_MEMALLOC WARN triggered from kswapd in 6.12.19.
>
> Does overlayfs need some kind of background inode reclaim support?
Hey everyone, I know there was some off-list discussion last week at
LSFMM, but I don't think a definite solution has been proposed for the
below stacktrace.
What is the shrinker API policy wrt memory allocation and I/O? Should
overlayfs do something more like XFS and background reclaim to avoid
GFP_NOFAIL
allocations when kswapd is shrinking caches?
> Call Trace:
> <TASK>
> __alloc_pages_noprof+0x31c/0x330
> alloc_pages_mpol_noprof+0xe3/0x1d0
> folio_alloc_noprof+0x5b/0xa0
> __filemap_get_folio+0x1f3/0x380
> __getblk_slow+0xa3/0x1e0
> __ext4_get_inode_loc+0x121/0x4b0
> ext4_get_inode_loc+0x40/0xa0
> ext4_reserve_inode_write+0x39/0xc0
> __ext4_mark_inode_dirty+0x5b/0x220
> ext4_evict_inode+0x26d/0x690
> evict+0x112/0x2a0
> __dentry_kill+0x71/0x180
> dput+0xeb/0x1b0
> ovl_stack_put+0x2e/0x50 [overlay]
> ovl_destroy_inode+0x3a/0x60 [overlay]
> destroy_inode+0x3b/0x70
> __dentry_kill+0x71/0x180
> shrink_dentry_list+0x6b/0xe0
> prune_dcache_sb+0x56/0x80
> super_cache_scan+0x12c/0x1e0
> do_shrink_slab+0x13b/0x350
> shrink_slab+0x278/0x3a0
> shrink_node+0x328/0x880
> balance_pgdat+0x36d/0x740
> kswapd+0x1f0/0x380
> kthread+0xd2/0x100
> ret_from_fork+0x34/0x50
> ret_from_fork_asm+0x1a/0x30
> </TASK>
next prev parent reply other threads:[~2025-04-03 12:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 2:42 Potential Linux Crash: WARNING in ext4_dirty_folio in Linux kernel v6.13-rc5 Luka
2025-03-06 5:13 ` Matthew Wilcox
2025-03-26 10:59 ` Matt Fleming
2025-04-03 12:29 ` Matt Fleming [this message]
2025-04-03 12:58 ` Vlastimil Babka
2025-04-03 14:33 ` Michal Hocko
2025-04-03 17:12 ` Matthew Wilcox
2025-04-03 19:32 ` James Bottomley
2025-04-04 9:09 ` Vlastimil Babka
2025-04-04 13:50 ` Matthew Wilcox
2025-04-07 23:00 ` Dave Chinner
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=CAENh_SSbkoa3srjkAMmJuf-iTFxHOtwESHoXiPAu6bO7MLOkDA@mail.gmail.com \
--to=matt@readmodwrite.com \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=amir73il@gmail.com \
--cc=baohua@kernel.org \
--cc=david@fromorbit.com \
--cc=kernel-team@cloudflare.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luka.2016.cs@gmail.com \
--cc=miklos@szeredi.hu \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=tytso@mit.edu \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
--cc=zhengqi.arch@bytedance.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).