From: Dev Jain <dev.jain@arm.com>
To: Shivank Garg <shivankg@amd.com>,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@redhat.com>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: Zi Yan <ziy@nvidia.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Nico Pache <npache@redhat.com>,
Ryan Roberts <ryan.roberts@arm.com>,
Barry Song <baohua@kernel.org>, Lance Yang <lance.yang@linux.dev>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Zach O'Keefe <zokeefe@google.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] mm/khugepaged: return EAGAIN for transient dirty pages in MADV_COLLAPSE
Date: Mon, 10 Nov 2025 19:16:40 +0530 [thread overview]
Message-ID: <4ab54ae0-2607-443d-8698-788d8e951bdd@arm.com> (raw)
In-Reply-To: <20251110113254.77822-3-shivankg@amd.com>
On 10/11/25 5:02 pm, Shivank Garg wrote:
> When MADV_COLLAPSE encounters dirty file-backed pages, it currently
> returns -EINVAL, this is misleading as EINVAL suggests invalid arguments,
> whereas dirty pages are a transient condition that may resolve on retry.
>
> Introduce SCAN_PAGE_DIRTY and map it to -EAGAIN. For khugepaged, this
> is harmless as it will revisit the range after async writeback completes.
Taking a cursory look at enum scan_result, I am sure there are other error
codes as well which redirect to -EINVAL when they actually should to something
else...
>
> Signed-off-by: Shivank Garg <shivankg@amd.com>
> ---
> include/trace/events/huge_memory.h | 3 ++-
> mm/khugepaged.c | 4 +++-
> 2 files changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/include/trace/events/huge_memory.h b/include/trace/events/huge_memory.h
> index dd94d14a2427..9014a9bbe64c 100644
> --- a/include/trace/events/huge_memory.h
> +++ b/include/trace/events/huge_memory.h
> @@ -38,7 +38,8 @@
> EM( SCAN_PAGE_HAS_PRIVATE, "page_has_private") \
> EM( SCAN_STORE_FAILED, "store_failed") \
> EM( SCAN_COPY_MC, "copy_poisoned_page") \
> - EMe(SCAN_PAGE_FILLED, "page_filled")
> + EM(SCAN_PAGE_FILLED, "page_filled") \
> + EMe(SCAN_PAGE_DIRTY, "page_dirty")
>
> #undef EM
> #undef EMe
> diff --git a/mm/khugepaged.c b/mm/khugepaged.c
> index d08ed6eb9ce1..7df329c9c87d 100644
> --- a/mm/khugepaged.c
> +++ b/mm/khugepaged.c
> @@ -60,6 +60,7 @@ enum scan_result {
> SCAN_STORE_FAILED,
> SCAN_COPY_MC,
> SCAN_PAGE_FILLED,
> + SCAN_PAGE_DIRTY,
> };
>
> #define CREATE_TRACE_POINTS
> @@ -1967,7 +1968,7 @@ static int collapse_file(struct mm_struct *mm, unsigned long addr,
> */
> xas_unlock_irq(&xas);
> filemap_flush(mapping);
> - result = SCAN_FAIL;
> + result = SCAN_PAGE_DIRTY;
> goto xa_unlocked;
> } else if (folio_test_writeback(folio)) {
> xas_unlock_irq(&xas);
Now that you are at it, it would make sense to redirect this folio_test_writeback()
branch also to -EAGAIN, and call the common error code SCAN_PAGE_UNDER_WRITEBACK.
> @@ -2747,6 +2748,7 @@ static int madvise_collapse_errno(enum scan_result r)
> case SCAN_PAGE_LRU:
> case SCAN_DEL_PAGE_LRU:
> case SCAN_PAGE_FILLED:
> + case SCAN_PAGE_DIRTY:
> return -EAGAIN;
> /*
> * Other: Trying again likely not to succeed / error intrinsic to
next prev parent reply other threads:[~2025-11-10 13:46 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 11:32 [PATCH 1/2] mm/khugepaged: do synchronous writeback for MADV_COLLAPSE Shivank Garg
2025-11-10 11:32 ` [PATCH 2/2] mm/khugepaged: return EAGAIN for transient dirty pages in MADV_COLLAPSE Shivank Garg
2025-11-10 11:56 ` Lorenzo Stoakes
2025-11-19 10:25 ` Garg, Shivank
2025-11-19 18:16 ` Lorenzo Stoakes
2025-11-20 7:03 ` Garg, Shivank
2025-11-10 13:46 ` Dev Jain [this message]
2025-11-19 7:00 ` Garg, Shivank
2025-11-10 12:01 ` [PATCH 1/2] mm/khugepaged: do synchronous writeback for MADV_COLLAPSE Lorenzo Stoakes
2025-11-10 13:07 ` Garg, Shivank
2025-11-10 13:22 ` Lorenzo Stoakes
2025-11-10 16:06 ` Lorenzo Stoakes
2025-11-10 16:55 ` Zi Yan
2025-11-10 19:40 ` Garg, Shivank
2025-11-10 19:48 ` Lorenzo Stoakes
2025-11-10 19:53 ` Lorenzo Stoakes
2025-11-10 21:16 ` Lorenzo Stoakes
2025-11-10 21:56 ` Zi Yan
2025-11-10 22:03 ` Lorenzo Stoakes
2025-11-11 5:26 ` Garg, Shivank
2025-11-10 13:24 ` Dev Jain
2025-11-10 13:36 ` Lorenzo Stoakes
2025-11-11 3:41 ` Dev Jain
2025-11-10 13:47 ` Matthew Wilcox
2025-11-10 13:52 ` Lorenzo Stoakes
2025-11-10 14:17 ` Matthew Wilcox
2025-11-10 14:20 ` Garg, Shivank
2025-11-10 14:23 ` Lorenzo Stoakes
2025-11-10 14:28 ` Matthew Wilcox
2025-11-11 5:58 ` Garg, Shivank
2025-11-13 15:30 ` David Hildenbrand (Red Hat)
2025-11-10 14:00 ` David Hildenbrand (Red Hat)
2025-11-10 14:03 ` Matthew Wilcox
2025-11-10 14:05 ` Lorenzo Stoakes
2025-11-10 14:54 ` David Hildenbrand (Red Hat)
2025-11-13 14:21 ` kernel test robot
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=4ab54ae0-2607-443d-8698-788d8e951bdd@arm.com \
--to=dev.jain@arm.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@redhat.com \
--cc=lance.yang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=npache@redhat.com \
--cc=rostedt@goodmis.org \
--cc=ryan.roberts@arm.com \
--cc=shivankg@amd.com \
--cc=ziy@nvidia.com \
--cc=zokeefe@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®