[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <deb6c0a2-e166-4c91-9736-276c9f1741c9@redhat.com>
Date: Tue, 7 Oct 2025 09:04:59 +0200
From: David Hildenbrand <david@...hat.com>
To: Yunseong Kim <ysk@...lloc.com>, Byungchul Park <byungchul@...com>,
Hillf Danton <hdanton@...a.com>
Cc: akpm@...ux-foundation.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, kernel_team@...ynix.com,
Yeoreum Yun <yeoreum.yun@....com>
Subject: Re: [RFC] mm/migrate: make sure folio_unlock() before
folio_wait_writeback()
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
probably getting something wrong)?
--
Cheers
David / dhildenb
Powered by blists - more mailing lists