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 449C6C021B2 for ; Fri, 21 Feb 2025 01:54:11 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id D504E28001A; Thu, 20 Feb 2025 20:54:10 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id D267F28000B; Thu, 20 Feb 2025 20:54:10 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id BC86D28001A; Thu, 20 Feb 2025 20:54:10 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0015.hostedemail.com [216.40.44.15]) by kanga.kvack.org (Postfix) with ESMTP id 98F7C28000B for ; Thu, 20 Feb 2025 20:54:10 -0500 (EST) Received: from smtpin28.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay05.hostedemail.com (Postfix) with ESMTP id 4C95B4B5D7 for ; Fri, 21 Feb 2025 01:54:10 +0000 (UTC) X-FDA: 83142281460.28.0A8B348 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by imf26.hostedemail.com (Postfix) with ESMTP id DC20A140004 for ; Fri, 21 Feb 2025 01:54:07 +0000 (UTC) Authentication-Results: imf26.hostedemail.com; dkim=pass header.d=redhat.com header.s=mimecast20190719 header.b=OlvVn42H; dmarc=pass (policy=none) header.from=redhat.com; spf=pass (imf26.hostedemail.com: domain of peterx@redhat.com designates 170.10.133.124 as permitted sender) smtp.mailfrom=peterx@redhat.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1740102848; a=rsa-sha256; cv=none; b=5UEdWXEqUpkTPbhmma5IK+nVJFTXJwgyq7kJejIQHYcDjPZXcwm3MF5dFRaS+cTOy4+UTD jg1jWsMYk0zRo9+xntUViC0YsZ7VgZN9lb3DSAiNEMmZE1yNBJ6ZGYCOAE8dbEjGJvlgAw W719DAvBPeZLjo3p2uobxnryPrY74+s= ARC-Authentication-Results: i=1; imf26.hostedemail.com; dkim=pass header.d=redhat.com header.s=mimecast20190719 header.b=OlvVn42H; dmarc=pass (policy=none) header.from=redhat.com; spf=pass (imf26.hostedemail.com: domain of peterx@redhat.com designates 170.10.133.124 as permitted sender) smtp.mailfrom=peterx@redhat.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1740102848; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=5OAFXYnALRZTyV+LNguXtTPvraFsCYlDyGOu4JUK444=; b=amVifT3vZ1caW/Oyp832zTHNk37ju9vnwjpGhfKsM3p1huDRBSk0RD0ktsI7KraTipZ/qo dXNYDX2GqQoRjruJIMxeYIA+fPohlI8ea99fRni7dv4qgg4tvBSxRlnmSSt/8fkN5IBH2Z DN48Pgco9ZhBKW8Xu7s6snhG+jjDHlQ= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1740102847; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=5OAFXYnALRZTyV+LNguXtTPvraFsCYlDyGOu4JUK444=; b=OlvVn42HcbKIJRxdhZvZi8eSR8DCpRRlz+xTAHXwebmhDeA3DLUUwdmqSc/3OG6ITP25i5 gqSQRwq0/S34dSI+VH1RILgMZJoeDh+Q4SBvLJllYyV8rM/y6x033KyQjvOFJSGb+YoLpH 0qEFmhYL9E0B6Es0KLBwfF4V6Uj8AGU= Received: from mail-qt1-f198.google.com (mail-qt1-f198.google.com [209.85.160.198]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-682-GQyk05k0PEKmZrcz9La-NQ-1; Thu, 20 Feb 2025 20:54:06 -0500 X-MC-Unique: GQyk05k0PEKmZrcz9La-NQ-1 X-Mimecast-MFC-AGG-ID: GQyk05k0PEKmZrcz9La-NQ_1740102845 Received: by mail-qt1-f198.google.com with SMTP id d75a77b69052e-471faf6e4ffso32720361cf.1 for ; Thu, 20 Feb 2025 17:54:06 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1740102845; x=1740707645; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=5OAFXYnALRZTyV+LNguXtTPvraFsCYlDyGOu4JUK444=; b=POaSV++qKIPna+0jw5NwVkMQUDlNgSS5Dc1DP+gAdDqzv5UA2gS+2bZFCJtBY9UkL3 ihLfwTsA2LT/942VZMHldY9pfRWCEG/Foq/b31FhS7BAR6zXzVpUJyhurezEZRetRJ7x 2VY50nvUnj6KLAikRNEjGFB60h2OeXAlGpreW0Mk4izsDhaXvzgkt2OJLC4qYfk2wkwG qIaZPb8lsDx9ZDG6vnLuppGKdqGQzHcHSltPz7tPpCaBBUv9vi2S4TjJZ2SEHUZNo2VP B5vzXIhSCQ4hnA3299hzky7EiPg5eQMlFo+CXF1RXP7oWohyvu2N2Fzw9sYkQQDNHglz 9qyw== X-Forwarded-Encrypted: i=1; AJvYcCVg7uIfRtd8vb/7ES+qZ/ny/l7Rj9+0f+XJB4CYIR4fS9WzQZuBotlTbPzOoSBZ6nZ8StFA378iBw==@kvack.org X-Gm-Message-State: AOJu0YwsNlG7ff0eVTXvhENjkIsbJPN+82o/8/dMzX12Oubsl6uim9es l0soXGuOb/JpHwgN10LQvdEyF49fcpVhTY45+H0v8jIMyP5frwFp/FDK8cEAYUOCNNblO/rJ4pf 9hARwCw1rxjE3KY2tA1hRvhRldvBKeVbBpekVDVsbv60rzbiFNzF0a9aD X-Gm-Gg: ASbGnctJ3aRYQi3uyRRzXgpq1ItbdH2YucKiaskabtaqvjufv+33bM2wpXELavRl+Yg ZGW8TYDLTchJ1ttuSkQiA7bWodQtB9muR9Ncb0kCQBqNJNIjXnDtmVB+75zrjFJ86NALGPWlLRt UzeUNuqXIKakzPpsPw9yP3h0606TmsdBp8mF/C7XfP6M1yWxwJJFdpY+a70kNFv+VvwW7vJmVvo 5TUg+qff89ko+Fuyb0hELZRWYa7kN0dFgQv/S0zYpQUfEP35uc939iLygmeAp3JdKPhgQ== X-Received: by 2002:a05:622a:252:b0:472:d35:6004 with SMTP id d75a77b69052e-472249072afmr14859011cf.50.1740102845152; Thu, 20 Feb 2025 17:54:05 -0800 (PST) X-Google-Smtp-Source: AGHT+IE3boZYPdobPm9o/YjX/wkHkkiexeB/6RDhOZf6LJhMj2dbl+gb5I4Is59rlw9q5wOfgif13g== X-Received: by 2002:a05:622a:252:b0:472:d35:6004 with SMTP id d75a77b69052e-472249072afmr14858711cf.50.1740102844689; Thu, 20 Feb 2025 17:54:04 -0800 (PST) Received: from x1.local ([2604:7a40:2041:2b00::1000]) by smtp.gmail.com with ESMTPSA id d75a77b69052e-47201c9eecesm35363631cf.37.2025.02.20.17.54.02 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 20 Feb 2025 17:54:04 -0800 (PST) Date: Thu, 20 Feb 2025 20:54:00 -0500 From: Peter Xu To: Barry Song <21cnbao@gmail.com> Cc: Suren Baghdasaryan , Lokesh Gidra , linux-mm@kvack.org, akpm@linux-foundation.org, linux-kernel@vger.kernel.org, zhengtangquan@oppo.com, Barry Song , Andrea Arcangeli , Al Viro , Axel Rasmussen , Brian Geffon , Christian Brauner , David Hildenbrand , Hugh Dickins , Jann Horn , Kalesh Singh , "Liam R . Howlett" , Matthew Wilcox , Michal Hocko , Mike Rapoport , Nicolas Geoffray , Ryan Roberts , Shuah Khan , ZhangPeng , Yu Zhao Subject: Re: [PATCH RFC] mm: Fix kernel BUG when userfaultfd_move encounters swapcache Message-ID: References: <20250219112519.92853-1-21cnbao@gmail.com> MIME-Version: 1.0 In-Reply-To: X-Mimecast-Spam-Score: 0 X-Mimecast-MFC-PROC-ID: iqvFk8M7og-8jH2OSldNDDMb0JaDUOiWh9uvIcz_8W0_1740102845 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-Rspamd-Server: rspam02 X-Rspamd-Queue-Id: DC20A140004 X-Stat-Signature: a4oq1r318f956bgs3q7bd9nedxhyy4fz X-Rspam-User: X-HE-Tag: 1740102847-436347 X-HE-Meta: U2FsdGVkX1+/4vhjI1LlldOYEIQ/3mS9aOeAMm8NP6Q38tPFtJbYICdXsSU0zquSGiA+Up3SjMiC83RCZ3a3xOVZMfM35Vh1EZOe5PmvwRRG+BpTug0FxklxOms+PDbgL8qQLRdfq3xfiYvzt3F1xnX+3wGG2jpbBp5ny1SCdxYKaJLM9W28ZVk5JLax5FjRH610Nwsy0b22hx33CEOtq6mq+G5FQ0yvwcv9BC62OyLgJ53ZXz9GEtJ8JwxS3MST1Bovs+dZYJMZxemMbzVD6GqL7sUNG93gn/YOE9WSDv8u+2w/C2FLFmA7WCMU2ey/gS98gC00HlqeNiKCYkBausVfFW4Pkcx/cH0/yEQMfmgl8GNSPiIXAAb01RRhdhyBtUUjk5q0Ue1KcjxNfMhiZzHEXtVxmN0gz6kNXIwDiORWlUrkAJUJBjCCCeuZ/lctRK/11+7U797WU9kfqF1FYuSEeYXAPJCyf+nxBgcHY9zUnApHDyXcvG7cRh9NTJCpM7TdETJaQCqqAfuRfFdjY4jlUd650HV/XksNDG9yaw/XAQ0Sqt3bx6/eaxrOJQW0CdlGZ009sdgtphPj+vn1d55Dn0okX0mLNFd2ngZ1E6NmfjrvPtcMWx3PDfn7ENLAJMTTgvcbs+wXZKrOryhUusIBkJAZtVyJyDnk0Ef4nP6r1YUWnj7h1SLqSOemyvyWyvMbQcFW4HGI+YUSDccO+ytVtWzQ//YyXWnZa72ZT9X18Gge0ENYSYmQerh7PBjrAUnMNEf+7AqSZ19LyOjjraz4i7N9SttXoktDD9xQMyiWejCphEBqXsI1mqgN/rd+BpiWMjPAutbqJe9rl2gWn9bLBoW3SWQr+D49ATMDpk3QVy0rVYUybIpbYvs1tWH1G9SDW8T/Px5m6b3s25DA3z7NNlYGxpAeL2pCiharP9OC6IduvJdkyaG6R1G3mSedxd+edO85CNOp7JJOJUt FOEq3Prd cie6hyP9twXT1cTjVMQ0bMvPLb2SGYASEd5JcRskMOC5OY5ianDAF3dM7wZgx+gxd3OpSScmfAXnv0k4sSR8KgXXgeG8+FQNqWA4v9dj1LRTYAZfCgOr0kKXKX9Ild4DJnprfC7NoW+k8V9tbZ6UJ6iINxhCc/hCVw/u2go2Gbfmc/loe/+vXalBxRpI46YG5TV0DRZppLn52YFPYr+gK8/d+i9phY34NVBnSLTmY3Yf+m8zOT53lokBOX2A4NJRfcsNuc8VrrgBtCBUpGuSIGEq9g5owxZd4KvnptmdSYKk4Kg3jkIW77PfQW+zT/17IuXmorVloJ/EeM/yE8Lse/Hcl2tSWRHekCwFgV1n4NKe+lPLa/ZF0QwSYgv/b3jGtbZq8jqNzG+iS4zQp1OgEIgpwOS1ZYii8pEyf75DeTlmXAsb0CvjDDR7UTPmg9fPg4r6d4Ra10tm/UveRppN1zoVU+/zhyPWAQ+q/9SEM6ovkUQP7ljLVe2UsGdrzHvh7DoYvgeVWOzk2Eap/znj5Pc+M7A== 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: On Fri, Feb 21, 2025 at 02:36:27PM +1300, Barry Song wrote: > On Fri, Feb 21, 2025 at 11:59 AM Peter Xu wrote: > > > > On Thu, Feb 20, 2025 at 12:04:40PM +1300, Barry Song wrote: > > > On Thu, Feb 20, 2025 at 11:15 AM Peter Xu wrote: > > > > > > > > On Thu, Feb 20, 2025 at 09:37:50AM +1300, Barry Song wrote: > > > > > On Thu, Feb 20, 2025 at 7:27 AM Suren Baghdasaryan wrote: > > > > > > > > > > > > On Wed, Feb 19, 2025 at 3:25 AM Barry Song <21cnbao@gmail.com> wrote: > > > > > > > > > > > > > > From: Barry Song > > > > > > > > > > > > > > userfaultfd_move() checks whether the PTE entry is present or a > > > > > > > swap entry. > > > > > > > > > > > > > > - If the PTE entry is present, move_present_pte() handles folio > > > > > > > migration by setting: > > > > > > > > > > > > > > src_folio->index = linear_page_index(dst_vma, dst_addr); > > > > > > > > > > > > > > - If the PTE entry is a swap entry, move_swap_pte() simply copies > > > > > > > the PTE to the new dst_addr. > > > > > > > > > > > > > > This approach is incorrect because even if the PTE is a swap > > > > > > > entry, it can still reference a folio that remains in the swap > > > > > > > cache. > > > > > > > > > > > > > > If do_swap_page() is triggered, it may locate the folio in the > > > > > > > swap cache. However, during add_rmap operations, a kernel panic > > > > > > > can occur due to: > > > > > > > page_pgoff(folio, page) != linear_page_index(vma, address) > > > > > > > > > > > > Thanks for the report and reproducer! > > > > > > > > > > > > > > > > > > > > $./a.out > /dev/null > > > > > > > [ 13.336953] page: refcount:6 mapcount:1 mapping:00000000f43db19c index:0xffffaf150 pfn:0x4667c > > > > > > > [ 13.337520] head: order:2 mapcount:1 entire_mapcount:0 nr_pages_mapped:1 pincount:0 > > > > > > > [ 13.337716] memcg:ffff00000405f000 > > > > > > > [ 13.337849] anon flags: 0x3fffc0000020459(locked|uptodate|dirty|owner_priv_1|head|swapbacked|node=0|zone=0|lastcpupid=0xffff) > > > > > > > [ 13.338630] raw: 03fffc0000020459 ffff80008507b538 ffff80008507b538 ffff000006260361 > > > > > > > [ 13.338831] raw: 0000000ffffaf150 0000000000004000 0000000600000000 ffff00000405f000 > > > > > > > [ 13.339031] head: 03fffc0000020459 ffff80008507b538 ffff80008507b538 ffff000006260361 > > > > > > > [ 13.339204] head: 0000000ffffaf150 0000000000004000 0000000600000000 ffff00000405f000 > > > > > > > [ 13.339375] head: 03fffc0000000202 fffffdffc0199f01 ffffffff00000000 0000000000000001 > > > > > > > [ 13.339546] head: 0000000000000004 0000000000000000 00000000ffffffff 0000000000000000 > > > > > > > [ 13.339736] page dumped because: VM_BUG_ON_PAGE(page_pgoff(folio, page) != linear_page_index(vma, address)) > > > > > > > [ 13.340190] ------------[ cut here ]------------ > > > > > > > [ 13.340316] kernel BUG at mm/rmap.c:1380! > > > > > > > [ 13.340683] Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP > > > > > > > [ 13.340969] Modules linked in: > > > > > > > [ 13.341257] CPU: 1 UID: 0 PID: 107 Comm: a.out Not tainted 6.14.0-rc3-gcf42737e247a-dirty #299 > > > > > > > [ 13.341470] Hardware name: linux,dummy-virt (DT) > > > > > > > [ 13.341671] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) > > > > > > > [ 13.341815] pc : __page_check_anon_rmap+0xa0/0xb0 > > > > > > > [ 13.341920] lr : __page_check_anon_rmap+0xa0/0xb0 > > > > > > > [ 13.342018] sp : ffff80008752bb20 > > > > > > > [ 13.342093] x29: ffff80008752bb20 x28: fffffdffc0199f00 x27: 0000000000000001 > > > > > > > [ 13.342404] x26: 0000000000000000 x25: 0000000000000001 x24: 0000000000000001 > > > > > > > [ 13.342575] x23: 0000ffffaf0d0000 x22: 0000ffffaf0d0000 x21: fffffdffc0199f00 > > > > > > > [ 13.342731] x20: fffffdffc0199f00 x19: ffff000006210700 x18: 00000000ffffffff > > > > > > > [ 13.342881] x17: 6c203d2120296567 x16: 6170202c6f696c6f x15: 662866666f67705f > > > > > > > [ 13.343033] x14: 6567617028454741 x13: 2929737365726464 x12: ffff800083728ab0 > > > > > > > [ 13.343183] x11: ffff800082996bf8 x10: 0000000000000fd7 x9 : ffff80008011bc40 > > > > > > > [ 13.343351] x8 : 0000000000017fe8 x7 : 00000000fffff000 x6 : ffff8000829eebf8 > > > > > > > [ 13.343498] x5 : c0000000fffff000 x4 : 0000000000000000 x3 : 0000000000000000 > > > > > > > [ 13.343645] x2 : 0000000000000000 x1 : ffff0000062db980 x0 : 000000000000005f > > > > > > > [ 13.343876] Call trace: > > > > > > > [ 13.344045] __page_check_anon_rmap+0xa0/0xb0 (P) > > > > > > > [ 13.344234] folio_add_anon_rmap_ptes+0x22c/0x320 > > > > > > > [ 13.344333] do_swap_page+0x1060/0x1400 > > > > > > > [ 13.344417] __handle_mm_fault+0x61c/0xbc8 > > > > > > > [ 13.344504] handle_mm_fault+0xd8/0x2e8 > > > > > > > [ 13.344586] do_page_fault+0x20c/0x770 > > > > > > > [ 13.344673] do_translation_fault+0xb4/0xf0 > > > > > > > [ 13.344759] do_mem_abort+0x48/0xa0 > > > > > > > [ 13.344842] el0_da+0x58/0x130 > > > > > > > [ 13.344914] el0t_64_sync_handler+0xc4/0x138 > > > > > > > [ 13.345002] el0t_64_sync+0x1ac/0x1b0 > > > > > > > [ 13.345208] Code: aa1503e0 f000f801 910f6021 97ff5779 (d4210000) > > > > > > > [ 13.345504] ---[ end trace 0000000000000000 ]--- > > > > > > > [ 13.345715] note: a.out[107] exited with irqs disabled > > > > > > > [ 13.345954] note: a.out[107] exited with preempt_count 2 > > > > > > > > > > > > > > Fully fixing it would be quite complex, requiring similar handling > > > > > > > of folios as done in move_present_pte. > > > > > > > > > > > > How complex would that be? Is it a matter of adding > > > > > > folio_maybe_dma_pinned() checks, doing folio_move_anon_rmap() and > > > > > > folio->index = linear_page_index like in move_present_pte() or > > > > > > something more? > > > > > > > > > > My main concern is still with large folios that require a split_folio() > > > > > during move_pages(), as the entire folio shares the same index and > > > > > anon_vma. However, userfaultfd_move() moves pages individually, > > > > > making a split necessary. > > > > > > > > > > However, in split_huge_page_to_list_to_order(), there is a: > > > > > > > > > > if (folio_test_writeback(folio)) > > > > > return -EBUSY; > > > > > > > > > > This is likely true for swapcache, right? However, even for move_present_pte(), > > > > > it simply returns -EBUSY: > > > > > > > > > > move_pages_pte() > > > > > { > > > > > /* at this point we have src_folio locked */ > > > > > if (folio_test_large(src_folio)) { > > > > > /* split_folio() can block */ > > > > > pte_unmap(&orig_src_pte); > > > > > pte_unmap(&orig_dst_pte); > > > > > src_pte = dst_pte = NULL; > > > > > err = split_folio(src_folio); > > > > > if (err) > > > > > goto out; > > > > > > > > > > /* have to reacquire the folio after it got split */ > > > > > folio_unlock(src_folio); > > > > > folio_put(src_folio); > > > > > src_folio = NULL; > > > > > goto retry; > > > > > } > > > > > } > > > > > > > > > > Do we need a folio_wait_writeback() before calling split_folio()? > > > > > > > > Maybe no need in the first version to fix the immediate bug? > > > > > > > > It's also not always the case to hit writeback here. IIUC, writeback only > > > > happens for a short window when the folio was just added into swapcache. > > > > MOVE can happen much later after that anytime before a swapin. My > > > > understanding is that's also what Matthew wanted to point out. It may be > > > > better justified of that in a separate change with some performance > > > > measurements. > > > > > > The bug we’re discussing occurs precisely within the short window you > > > mentioned. > > > > > > 1. add_to_swap: The folio is added to swapcache. > > > 2. try_to_unmap: PTEs are converted to swap entries. > > > 3. pageout > > > 4. Swapcache is cleared. > > > > Hmm, I see. I was expecting step 4 to be "writeback is cleared".. or at > > least that should be step 3.5, as IIUC "writeback" needs to be cleared > > before "swapcache" bit being cleared. > > > > > > > > The issue happens between steps 2 and 4, where the PTE is not present, but > > > the folio is still in swapcache - the current code does move_swap_pte() but does > > > not fixup folio->index within swapcache. > > > > One thing I'm still not clear here is why it's a race condition, rather > > than more severe than that. I mean, folio->index is definitely wrong, then > > as long as the page still in swapcache, we should be able to move the swp > > entry over to dest addr of UFFDIO_MOVE, read on dest addr, then it'll see > > the page in swapcache with the wrong folio->index already and trigger. > > > > I wrote a quick test like that, it actually won't trigger.. > > > > I had a closer look in the code, I think it's because do_swap_page() has > > the logic to detect folio->index matching first, and allocate a new folio > > if it doesn't match in ksm_might_need_to_copy(). IIUC that was for > > ksm.. but it looks like it's functioning too here. > > > > ksm_might_need_to_copy: > > if (folio_test_ksm(folio)) { > > if (folio_stable_node(folio) && > > !(ksm_run & KSM_RUN_UNMERGE)) > > return folio; /* no need to copy it */ > > } else if (!anon_vma) { > > return folio; /* no need to copy it */ > > } else if (folio->index == linear_page_index(vma, addr) && <---------- [1] > > anon_vma->root == vma->anon_vma->root) { > > return folio; /* still no need to copy it */ > > } > > ... > > > > new_folio = vma_alloc_folio(GFP_HIGHUSER_MOVABLE, 0, vma, addr); <---- [2] > > ... > > > > So I believe what I hit is at [1] it sees index doesn't match, then it > > decided to allocate a new folio. In this case, it won't hit your BUG > > because it'll be "folio != swapcache" later, so it'll setup the > > folio->index for the new one, rather than the sanity check. > > You're absolutely right. The problem goes beyond just crashes; we're > also dealing with CoW when KSM is enabled. As long as we disable > KSM(which is true for Android), or when we are dealing with a large folio, > ksm_might_need_to_copy() will not allocate a new copy: Ah! That explains it.. > > struct folio *ksm_might_need_to_copy(struct folio *folio, > struct vm_area_struct *vma, unsigned long addr) > { > > struct page *page = folio_page(folio, 0); > struct anon_vma *anon_vma = folio_anon_vma(folio); > struct folio *new_folio; > > if (folio_test_large(folio)) > return folio; > .... > } > > Thanks for your great findings! For the KSM-enabled and small folio case, > it's pretty funny how UFFDIO_MOVE finally turns into a new allocation and > copy— somehow automatically falling back to "UFFDIO_COPY" :-) > It's amusing, but debugging it is fun. > > I'll add your findings to the changelog when I formally send v2, after gathering > all the code refinement suggestions and implementing the improvements. Thanks, that'll be helpful. I wanted to try with !KSM build but it's pretty late today (and it's company-wise PTO tomorrow..). Just in case useful, this is the reproducer I mentioned that didn't yet trigger when with KSM: https://github.com/xzpeter/clibs/blob/master/uffd-test/uffd-move-bug.c I'm not sure whether it'll also reproduce there, but there's chance it is a simpler reproducer. > > > > > Do you know how your case got triggered, being able to bypass the above [1] > > which should check folio->index already? > > > > > > > > My point is that if we want a proper fix for mTHP, we'd better handle writeback. > > > Otherwise, this isn’t much different from directly returning -EBUSY as proposed > > > in this RFC. > > > > > > For small folios, there’s no split_folio issue, making it relatively > > > simpler. Lokesh > > > mentioned plans to madvise NOHUGEPAGE in ART, so fixing small folios is likely > > > the first priority. > > > > Agreed. > > > > -- > > Peter Xu > > > > Thanks > Barry > -- Peter Xu