linux-kernel - Re: [RFC] mm/migrate: make sure folio_unlock() before folio_wait

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <bd88ec46-0588-4915-9737-15ddee4678ae@redhat.com>
Date: Mon, 13 Oct 2025 10:08:39 +0200
From: David Hildenbrand <david@...hat.com>
To: Byungchul Park <byungchul@...com>
Cc: Yunseong Kim <ysk@...lloc.com>, Hillf Danton <hdanton@...a.com>,
 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 13.10.25 06:36, Byungchul Park wrote:
> 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.

Okay, so some deadlock was triggered, but not the one described by DEPT, 
thanks.

-- 
Cheers

David / dhildenb