From: Byungchul Park <byungchul@sk.com>
To: David Hildenbrand <david@redhat.com>
Cc: Yunseong Kim <ysk@kzalloc.com>, Hillf Danton <hdanton@sina.com>,
akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, kernel_team@skhynix.com,
Yeoreum Yun <yeoreum.yun@arm.com>
Subject: Re: [RFC] mm/migrate: make sure folio_unlock() before folio_wait_writeback()
Date: Mon, 13 Oct 2025 13:36:31 +0900 [thread overview]
Message-ID: <20251013043631.GC6925@system.software.com> (raw)
In-Reply-To: <deb6c0a2-e166-4c91-9736-276c9f1741c9@redhat.com>
On Tue, Oct 07, 2025 at 09:04:59AM +0200, David Hildenbrand wrote:
> On 07.10.25 08:32, Yunseong Kim wrote:
> > Hi Hillf,
> >
> > Here are the syzlang and kernel log, and you can also find the gist snippet
> > in the body of the first RFC mail:
> >
> > https://gist.github.com/kzall0c/a6091bb2fd536865ca9aabfd017a1fc5
> >
> > I am reviewing this issue again on the v6.17, The issue is always reproducible,
> > usually occurring within about 10k attempts with the 8 procs.
>
> I can see a DEPT splat and I wonder what happens if DEPT is disabled.
>
> Will the machine actually deadlock or is this just DEPT complaining (and
Of course, it was an actual deadlock, not just DEPT splat.
However, even though this patch resolved the acutal hang issue, it
looked mismatched between the watchdog hang report and the DEPT report.
We are now re-checking it using the reproducer.
Byungchul
> probably getting something wrong)?
>
> --
> Cheers
>
> David / dhildenb
next prev parent reply other threads:[~2025-10-13 4:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 8:16 Byungchul Park
2025-10-02 11:38 ` David Hildenbrand
2025-10-02 22:02 ` Hillf Danton
2025-10-03 0:48 ` Byungchul Park
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 [this message]
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=20251013043631.GC6925@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 \
--cc=yeoreum.yun@arm.com \
--cc=ysk@kzalloc.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