From: Byungchul Park <byungchul@sk.com>
To: Hillf Danton <hdanton@sina.com>
Cc: David Hildenbrand <david@redhat.com>,
akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, kernel_team@skhynix.com
Subject: Re: [RFC] mm/migrate: make sure folio_unlock() before folio_wait_writeback()
Date: Fri, 3 Oct 2025 09:48:28 +0900 [thread overview]
Message-ID: <20251003004828.GA75385@system.software.com> (raw)
In-Reply-To: <20251002220211.8009-1-hdanton@sina.com>
On Fri, Oct 03, 2025 at 06:02:10AM +0800, Hillf Danton wrote:
> On Thu, 2 Oct 2025 13:38:59 +0200 David Hildenbrand wrote:
> >
> > If it's a real issue, I wonder if a trylock on the writeback path could
> > be an option.
> >
> Given Thanks to Yunseong for reporting the issue, testing, and confirming if
> this patch can resolve the issue, could you share your reproducer with
> reviewers Byungchul?
Sure. Yunseong told me it's 100% reproducable. Yunseong, can you help
him reproduce the issue, please?
Byungchul
next prev parent reply other threads:[~2025-10-03 0:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 8:16 [RFC] mm/migrate: make sure folio_unlock() before folio_wait_writeback() Byungchul Park
2025-10-02 11:38 ` David Hildenbrand
2025-10-02 22:02 ` Hillf Danton
2025-10-03 0:48 ` Byungchul Park [this message]
2025-10-03 0:52 ` Byungchul Park
2025-10-07 6:32 ` Yunseong Kim
2025-10-07 7:04 ` David Hildenbrand
2025-10-07 7:53 ` Yeoreum Yun
2025-10-13 4:36 ` Byungchul Park
2025-10-13 8:08 ` David Hildenbrand
2025-10-03 1:02 ` Byungchul Park
2025-10-03 2:31 ` Byungchul Park
2025-10-03 14:04 ` Pedro Falcato
2025-10-02 11:42 ` Yeoreum Yun
2025-10-02 11:49 ` Yeoreum Yun
2025-10-03 2:08 ` Byungchul Park
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=20251003004828.GA75385@system.software.com \
--to=byungchul@sk.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=hdanton@sina.com \
--cc=kernel_team@skhynix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.