From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 089D3C5B543 for ; Thu, 5 Jun 2025 07:38:04 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 56FCC6B0560; Thu, 5 Jun 2025 03:38:04 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 51FFB6B0561; Thu, 5 Jun 2025 03:38:04 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 40F406B0567; Thu, 5 Jun 2025 03:38:04 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0016.hostedemail.com [216.40.44.16]) by kanga.kvack.org (Postfix) with ESMTP id 1F34C6B0560 for ; Thu, 5 Jun 2025 03:38:04 -0400 (EDT) Received: from smtpin29.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay05.hostedemail.com (Postfix) with ESMTP id 96EAF8E61B for ; Thu, 5 Jun 2025 07:38:03 +0000 (UTC) X-FDA: 83520543246.29.F36BCCF Received: from szxga08-in.huawei.com (szxga08-in.huawei.com [45.249.212.255]) by imf10.hostedemail.com (Postfix) with ESMTP id 2990BC0003 for ; Thu, 5 Jun 2025 07:37:58 +0000 (UTC) Authentication-Results: imf10.hostedemail.com; dkim=none; spf=pass (imf10.hostedemail.com: domain of tujinjiang@huawei.com designates 45.249.212.255 as permitted sender) smtp.mailfrom=tujinjiang@huawei.com; dmarc=pass (policy=quarantine) header.from=huawei.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1749109082; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=ALUsEM9Ys3OU9dcn2UG3BCY/VMn4wNDXIj4CblCDVgk=; b=StoaPI0fAVN449qtkg/v1uGI8Wlo7bdWti4D4J2DltWADt0MHL2DQI7wwRkKRslFo9NHCv 1hjcuvRV+t5d0FQq6OP9aUEmFSHIm9UtJFlNpMFwCDDcoSxKIRvzLqOcECXdOCCLQp17C9 dzrl9+pfSqCofk9hVwcksUGqs+jJC1I= ARC-Authentication-Results: i=1; imf10.hostedemail.com; dkim=none; spf=pass (imf10.hostedemail.com: domain of tujinjiang@huawei.com designates 45.249.212.255 as permitted sender) smtp.mailfrom=tujinjiang@huawei.com; dmarc=pass (policy=quarantine) header.from=huawei.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1749109082; a=rsa-sha256; cv=none; b=TUfUydNN7pnLMEUAUeOYLwWdn4pIK9d8ueLtOmJB9evTSd6n33zfhdtGuLZnVx22LaUGdq dM5xJ0UIsMo55lgxsFgTIleWgLnMXx7lX+7gZURNd+z8WP4b5tLX1IXvX1iazduK6+Kogk TlqOudImozjPJihUH9T8X3o4suF3kU8= Received: from mail.maildlp.com (unknown [172.19.162.254]) by szxga08-in.huawei.com (SkyGuard) with ESMTP id 4bCbpm4G2Nz1d1DZ; Thu, 5 Jun 2025 15:36:00 +0800 (CST) Received: from kwepemo200002.china.huawei.com (unknown [7.202.195.209]) by mail.maildlp.com (Postfix) with ESMTPS id 0E939180236; Thu, 5 Jun 2025 15:37:55 +0800 (CST) Received: from [10.174.179.13] (10.174.179.13) by kwepemo200002.china.huawei.com (7.202.195.209) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Thu, 5 Jun 2025 15:37:54 +0800 Message-ID: <37e77dc4-bc73-2710-088f-f7ec0c787caf@huawei.com> Date: Thu, 5 Jun 2025 15:37:53 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.15.1 Subject: Re: [syzbot] [mm?] kernel BUG in try_to_unmap_one (2) To: David Hildenbrand , syzbot , , , , , , , , , , Jens Axboe , Catalin Marinas References: <68412d57.050a0220.2461cf.000e.GAE@google.com> <4fc2c008-2384-4d94-b1bf-f0a076585a4a@redhat.com> From: Jinjiang Tu In-Reply-To: Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit X-Originating-IP: [10.174.179.13] X-ClientProxiedBy: kwepems100001.china.huawei.com (7.221.188.238) To kwepemo200002.china.huawei.com (7.202.195.209) X-Rspamd-Server: rspam05 X-Rspamd-Queue-Id: 2990BC0003 X-Stat-Signature: a1c3t17wpredigtfpm43nt57whfckgng X-Rspam-User: X-HE-Tag: 1749109078-310413 X-HE-Meta: U2FsdGVkX19k5rN7ZbWQObQIIho74EVgxygX+MIAikhHwBs4Iue5Lp2Xj0qtb4LXzXFLeJsIR658Cq9W1RpIjoNnYic0fmk5w19l8t3LPOfPGFBki7ranq6oBqu0CoGVpkdBuCBmZB06hU3BlT4aTPq58D4egjYp5h66T4gQe2l861bLpJbTeO1pDj29/mE6RiYw3658GmHG6ieTwhztQgtI0CRhNbGvxCJI1GtZVKVxUW4ZpnLW7JfCWlnxKgnbtu0nU/PR1cLyz9bRRWoC6mI6ZptLkIoYFYMEepp0JfkGpG8Bm1ewcc/WUKgflR/SEdpcJ6wRkepwPR8s6BqQbIMOg6kCc259s1vYFTCyChFrKEiR2ep+VzdDdm41yhWHC/5yB6zLkiaItnsWd89QNAuhxniMRvtNNgI6sm93uj+q6sMBhSwltkT/jDx+rAZGhx952/ppGhZn4u6EoILY4TVyoMBbiKda2sjEqy0SVL2je34lVmBgVp6uxJZUrOj+pB5YAABocBGaFb/Snn9ZLjLLmObbo/aQWgR+WyNRoTTGizSzToJTmA5PTO2GhbvdE/OQi0OAQ9CJG4d4U1YcHLDsd0XWw0rKckca6SHROqVxjEJw4rwln8vuze3gBbv7+5hnBLG9YzyaHSkextwEN7CYd9j81L6J94HRblXI/ZdL7Gc1uupsqBT71thjwUpOaxbYIxONezC8xTfv5VCukCrNBTmRWgDqolCF33I8nrIUQTogotuH6P3RoqE5ZlsuvAwNyxEO94DkHejoUCg99NlmPkrfX6GZUqGZ35Iso+g67ml1eD8P9NwZ3lJetB1unRvGPwQTVlgjxUknJdd1yK9KglOP7xoWsWEqdsBxIsx3tbUl8j6Uy59JEd2LzRMXipaVRDNr30rJ4SeEiBGWv+rJlcqritn/R9NailOtql2rA2XxCDQxvvL7KgXq0LeBsA+x3PlIaAZwCct4eNa oqvc8Quz N/1ZRq+Kr2dqrIVoeERquTps/tSRqeyq7aTOqdmA2ADkDJRmqVzbED4kk9mUNajMQbEYHVfoB2h/ASSPy76pPyWtrVttOo21znRjaTaFTyZHBq4mpo1nLVmA8RQVOHZGQaPtjNwaiHk2GIsvMR5JU/Dl9ZN+GDoavFYWLHkOz29XsKPzHGL4kY53bLEtlJHrgXK9zc3Sl8pPyBJ5zElY6mveZmX/ozC1HD/1pLqJWgBG3ajlybPj+kfW0SvHFyEdKB1L3ePbgcCKkYdp+OgJJZx1UUCNOKN7DZe/a1szyjGvaFIjMDlSLnDF7P+9IJJZ4puyOySmBb9gnBzjUlFC+rkc+m9ZSqSG/OW+nouePAdwoMyIrPQ/pEG5FHyCAuOz35nHlNaQzu/53FCuh+rR+uPZRumhvrfdRZpAY X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: List-Subscribe: List-Unsubscribe: 在 2025/6/5 14:37, David Hildenbrand 写道: > On 05.06.25 08:27, David Hildenbrand wrote: >> On 05.06.25 08:11, David Hildenbrand wrote: >>> On 05.06.25 07:38, syzbot wrote: >>>> Hello, >>>> >>>> syzbot found the following issue on: >>>> >>>> HEAD commit:    d7fa1af5b33e Merge branch 'for-next/core' into >>>> for-kernelci >>> >>> Hmmm, another very odd page-table mapping related problem on that tree >>> found on arm64 only: >> >> In this particular reproducer we seem to be having MADV_HUGEPAGE and >> io_uring_setup() be racing with MADV_HWPOISON, MADV_PAGEOUT and >> io_uring_register(IORING_REGISTER_BUFFERS). >> >> I assume the issue is related to MADV_HWPOISON, MADV_PAGEOUT and >> io_uring_register racing, only. I suspect MADV_HWPOISON is trying to >> split a THP, while MADV_PAGEOUT tries paging it out. >> >> IORING_REGISTER_BUFFERS ends up in >> io_sqe_buffers_register->io_sqe_buffer_register where we GUP-fast and >> try coalescing buffers. >> >> And something about THPs is not particularly happy :) >> > > Not sure if realted to io_uring. > > unmap_poisoned_folio() calls try_to_unmap() without TTU_SPLIT_HUGE_PMD. > > When called from memory_failure(), we make sure to never call it on a > large folio: WARN_ON(folio_test_large(folio)); > > However, from shrink_folio_list() we might call unmap_poisoned_folio() > on a large folio, which doesn't work if it is still PMD-mapped. Maybe > passing TTU_SPLIT_HUGE_PMD would fix it. > > > Likely the relevant commit is: > > commit 1b0449544c6482179ac84530b61fc192a6527bfd > Author: Jinjiang Tu > Date:   Tue Mar 18 16:39:39 2025 +0800 > >     mm/vmscan: don't try to reclaim hwpoison folio >         Syzkaller reports a bug as follows: >         Injecting memory failure for pfn 0x18b00e at process virtual > address 0x20ffd000 >     Memory failure: 0x18b00e: dirty swapcache page still referenced by > 2 users >     Memory failure: 0x18b00e: recovery action for dirty swapcache > page: Failed >     page: refcount:2 mapcount:0 mapping:0000000000000000 index:0x20ffd > pfn:0x18b00e >     memcg:ffff0000dd6d9000 >     anon flags: > 0x5ffffe00482011(locked|dirty|arch_1|swapbacked|hwpoison|node=0|zone=2|lastcpupid=0xfffff) >     raw: 005ffffe00482011 dead000000000100 dead000000000122 > ffff0000e232a7c9 >     raw: 0000000000020ffd 0000000000000000 00000002ffffffff > ffff0000dd6d9000 >     page dumped because: VM_BUG_ON_FOLIO(!folio_test_uptodate(folio)) > > CCing Jinjiang Tu By the way, unmap_poisoned_folio() is called in do_migrate_range() too. the folio may be in lru and is a large folio.