From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Max Kellermann <max.kellermann@ionos.com>,
Christoph Hellwig <hch@lst.de>
Cc: Suren Baghdasaryan <surenb@google.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: Bad psi_group_cpu.tasks[NR_MEMSTALL] counter
Date: Thu, 21 Nov 2024 21:18:00 +0800 [thread overview]
Message-ID: <b8681f80-f2c5-44a0-b306-9f566dad65a6@linux.alibaba.com> (raw)
In-Reply-To: <CAKPOu+-_X9cc723v_f_BW4CwfHJe_mi=+cbUBP2tZO-kEcyoMA@mail.gmail.com>
Hi Max!
On 2024/11/21 16:43, Max Kellermann wrote:
> On Thu, Nov 21, 2024 at 5:51 AM Christoph Hellwig <hch@lst.de> wrote:
>> Something seems to be going wrong here, though, but the trace below
>> doesn't really tell me anything about the workload or file system
>> used, and if this is even calling into readahead.
>
> In case you were asking :-) these are web servers (shared webhosting),
> running PHP most of the time. The host itself runs on an ext4, but I
> don't think the ext4 system partition has anything to do with this.
> PHP runs in containers that are erofs, the PHP sources plus
> memory-mapped opcache files are in btrfs (read-only snapshot) and the
> runtime data is on NFS or Ceph (there have been stalls on both server
> types).
> My limited experience with Linux MM suggests that this happens during
> the page fault of a memory mapped file. PHP processes usually mmap
> only files from erofs and btrfs.
> The servers are always somewhat under memory pressure; our container
> manager keeps as many containers alive as possible and only shuts them
> down when the server reaches the memory limit. At any given time,
> there are thousands of containers.
Just saw this. I guess your _recent_ 6.11.9 bug is actually
related to EROFS since EROFS uses readahead_expand(). I think
your recent report was introduced by a recent backport fix
commit 9e2f9d34dd12 ("erofs: handle overlapped pclusters out of crafted images properly")
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.11.9&id=9cfa199bcbbbba31cbf97b2786f44f4464f3f29a
bio can be NULL after this patch and causes
unbalanced psi_memstall_{enter,leave}(). It can be fixed as
(the diff below could be damaged due to my email client):
diff --git a/fs/erofs/zdata.c b/fs/erofs/zdata.c
index 01f147505487..19ef4ff2a134 100644
--- a/fs/erofs/zdata.c
+++ b/fs/erofs/zdata.c
@@ -1792,9 +1792,9 @@ static void z_erofs_submit_queue(struct z_erofs_decompress_frontend *f,
erofs_fscache_submit_bio(bio);
else
submit_bio(bio);
- if (memstall)
- psi_memstall_leave(&pflags);
}
+ if (memstall)
+ psi_memstall_leave(&pflags);
/*
* although background is preferred, no one is pending for submission.
But your original report is without the very recent
commit 9e2f9d34dd12, before this commit bio cannot
be NULL so I don't think they are the same issue.
I will submit a formal fix for the recent bug later,
thanks!
Thanks,
Gao Xiang
next prev parent reply other threads:[~2024-11-21 13:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 7:16 Max Kellermann
2024-06-10 8:28 ` Max Kellermann
2024-06-12 5:01 ` Suren Baghdasaryan
2024-06-12 6:49 ` Max Kellermann
2024-06-12 9:48 ` Peter Zijlstra
2024-06-12 10:20 ` Max Kellermann
2024-11-21 14:02 ` Gao Xiang
2024-06-12 15:17 ` Suren Baghdasaryan
2024-08-05 12:34 ` Max Kellermann
2024-08-06 15:56 ` Suren Baghdasaryan
2024-08-12 8:06 ` Max Kellermann
2024-08-12 21:33 ` Suren Baghdasaryan
2024-11-20 16:30 ` Max Kellermann
2024-11-20 16:56 ` Suren Baghdasaryan
2024-11-21 4:51 ` Christoph Hellwig
2024-11-21 8:43 ` Max Kellermann
2024-11-21 13:18 ` Gao Xiang [this message]
2024-11-28 10:00 ` Max Kellermann
2024-11-28 10:46 ` Gao Xiang
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=b8681f80-f2c5-44a0-b306-9f566dad65a6@linux.alibaba.com \
--to=hsiangkao@linux.alibaba.com \
--cc=hannes@cmpxchg.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=max.kellermann@ionos.com \
--cc=peterz@infradead.org \
--cc=surenb@google.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
all inboxes | Powered by JetHome®