From patchwork Tue May 2 22:51:32 2023 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Lorenzo Stoakes X-Patchwork-Id: 13229328 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 00F6DC19F20 for ; Tue, 2 May 2023 22:51:42 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 5954A6B0078; Tue, 2 May 2023 18:51:42 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 545CE6B007B; Tue, 2 May 2023 18:51:42 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 40EE16B007D; Tue, 2 May 2023 18:51:42 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from mail-wr1-f51.google.com (mail-wr1-f51.google.com [209.85.221.51]) by kanga.kvack.org (Postfix) with ESMTP id E6CF96B0078 for ; Tue, 2 May 2023 18:51:41 -0400 (EDT) Received: by mail-wr1-f51.google.com with SMTP id ffacd0b85a97d-306281edf15so3737228f8f.1 for ; Tue, 02 May 2023 15:51:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683067901; x=1685659901; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:from:to:cc:subject:date:message-id:reply-to; bh=0RFhupXU1bVDFi2Y2FIy6WlZs49rrUCoImKiEbU0jvo=; b=KbXfX1YpJ3tkmT8YtdRC9HoMl1YE/eK+LnhF5IbskCq9S7Qr5LqD7EFO8WnchX8nXP /4S96bW4EGUKAWkr3ZI8rGsKueU31xL4nABuldtbsbFrB9igBXq3mN9Yacp6KP8obs1G A24s1xvtrIw+vufOrF0ROpZ2bM2yDMEg5ml0HRVwLYe+h06f8yHOrmN+jxyvhSOejJyX zcl2CWSDEy18B8+atq8HACVJAJVDdnxFDiC+fC5oI/JpwvvYsp8GsL3YL1ftq/Yf5Wht IjQx1mYdQZRNYDawu5lMk2ySbsjyWjLCbTXlEsVcRFt1lJLuCbRRoUViRj1rV0t3luYM qKrg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683067901; x=1685659901; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=0RFhupXU1bVDFi2Y2FIy6WlZs49rrUCoImKiEbU0jvo=; b=UUftuPoH9ueBzGTph0RX0ypWRxIQVbQkEvfV8PJVAlWFkRZyBTssZ850iXTrMaB6WV BzSN7qw7671Yf0lKhvWcA4Oixll5P25mXV5r0tE91Vo7Q+3IZXi9ldfnMxHou7pN9FZG 8TU8aBsKf7rLHt6hqXfjqHAhbHkvuXAqa4d0Hf6hFp4M/gMH7tIOCinVYiZTAxS6Vr/w e8B5F+dQ3NevV2+5waSPcw1PJ6AxZXHs9tpE1lTo4e21vCv554BT/r2yy4Zs27M3MOU/ VZAZQOnaEoT+Ua30VfWVHQ/h/yX9KaJ3Z95P0ic292lI7av4Q6YC3WaguwsNy6+B1FpZ U0RQ== X-Gm-Message-State: AC+VfDyuLoJNzhiUFUdYx+fOcKtDiwQGoVN7CgbPkuDPMJ7tHtw5999n mp6BUZknKvVcHKuUSedPeHvi5MDY7Dxn1g== X-Google-Smtp-Source: ACHHUZ4aNEsEcnXg6h3ToPZJd5Ca5o5oFljNZdZ5oOlNez9c4dOziY2F3dUyGU2FAp1Sp0P0Ez9ihw== X-Received: by 2002:a5d:4b0e:0:b0:304:a40c:43c6 with SMTP id v14-20020a5d4b0e000000b00304a40c43c6mr14850153wrq.11.1683067900566; Tue, 02 May 2023 15:51:40 -0700 (PDT) Received: from lucifer.home (host86-156-84-164.range86-156.btcentralplus.com. [86.156.84.164]) by smtp.googlemail.com with ESMTPSA id o18-20020a05600c379200b003f17300c7dcsm58143wmr.48.2023.05.02.15.51.37 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 02 May 2023 15:51:39 -0700 (PDT) From: Lorenzo Stoakes To: linux-mm@kvack.org, linux-kernel@vger.kernel.org, Andrew Morton Cc: Jason Gunthorpe , Jens Axboe , Matthew Wilcox , Dennis Dalessandro , Leon Romanovsky , Christian Benvenuti , Nelson Escobar , Bernard Metzler , Peter Zijlstra , Ingo Molnar , Arnaldo Carvalho de Melo , Mark Rutland , Alexander Shishkin , Jiri Olsa , Namhyung Kim , Ian Rogers , Adrian Hunter , Bjorn Topel , Magnus Karlsson , Maciej Fijalkowski , Jonathan Lemon , "David S . Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Christian Brauner , Richard Cochran , Alexei Starovoitov , Daniel Borkmann , Jesper Dangaard Brouer , John Fastabend , linux-fsdevel@vger.kernel.org, linux-perf-users@vger.kernel.org, netdev@vger.kernel.org, bpf@vger.kernel.org, Oleg Nesterov , Jason Gunthorpe , John Hubbard , Jan Kara , "Kirill A . Shutemov" , Pavel Begunkov , Mika Penttila , David Hildenbrand , Dave Chinner , Theodore Ts'o , Peter Xu , Matthew Rosato , "Paul E . McKenney" , Christian Borntraeger , Lorenzo Stoakes Subject: [PATCH v8 0/3] mm/gup: disallow GUP writing to file-backed mappings by default Date: Tue, 2 May 2023 23:51:32 +0100 Message-Id: X-Mailer: git-send-email 2.40.1 MIME-Version: 1.0 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: Writing to file-backed mappings which require folio dirty tracking using GUP is a fundamentally broken operation, as kernel write access to GUP mappings do not adhere to the semantics expected by a file system. A GUP caller uses the direct mapping to access the folio, which does not cause write notify to trigger, nor does it enforce that the caller marks the folio dirty. The problem arises when, after an initial write to the folio, writeback results in the folio being cleaned and then the caller, via the GUP interface, writes to the folio again. As a result of the use of this secondary, direct, mapping to the folio no write notify will occur, and if the caller does mark the folio dirty, this will be done so unexpectedly. For example, consider the following scenario:- 1. A folio is written to via GUP which write-faults the memory, notifying the file system and dirtying the folio. 2. Later, writeback is triggered, resulting in the folio being cleaned and the PTE being marked read-only. 3. The GUP caller writes to the folio, as it is mapped read/write via the direct mapping. 4. The GUP caller, now done with the page, unpins it and sets it dirty (though it does not have to). This change updates both the PUP FOLL_LONGTERM slow and fast APIs. As pin_user_pages_fast_only() does not exist, we can rely on a slightly imperfect whitelisting in the PUP-fast case and fall back to the slow case should this fail. v8: - Fixed typo writeable -> writable. - Fixed bug in writable_file_mapping_allowed() - must check combination of FOLL_PIN AND FOLL_LONGTERM not either/or. - Updated vma_needs_dirty_tracking() to include write/shared to account for MAP_PRIVATE mappings. - Move to open-coding the checks in folio_pin_allowed() so we can READ_ONCE() the mapping and avoid unexpected compiler loads. Rename to account for fact we now check flags here. - Disallow mapping == NULL or mapping & PAGE_MAPPING_FLAGS other than anon. Defer to slow path. - Perform GUP-fast check _after_ the lowest page table level is confirmed to be stable. - Updated comments and commit message for final patch as per Jason's suggestions. v7: - Fixed very silly bug in writeable_file_mapping_allowed() inverting the logic. - Removed unnecessary RCU lock code and replaced with adaptation of Peter's idea. - Removed unnecessary open-coded folio_test_anon() in folio_longterm_write_pin_allowed() and restructured to generally permit NULL folio_mapping(). https://lore.kernel.org/all/cover.1683044162.git.lstoakes@gmail.com/ v6: - Rebased on latest mm-unstable as of 28th April 2023. - Add PUP-fast check with handling for rcu-locked TLB shootdown to synchronise correctly. - Split patch series into 3 to make it more digestible. https://lore.kernel.org/all/cover.1682981880.git.lstoakes@gmail.com/ v5: - Rebased on latest mm-unstable as of 25th April 2023. - Some small refactorings suggested by John. - Added an extended description of the problem in the comment around writeable_file_mapping_allowed() for clarity. - Updated commit message as suggested by Mika and John. https://lore.kernel.org/all/6b73e692c2929dc4613af711bdf92e2ec1956a66.1682638385.git.lstoakes@gmail.com/ v4: - Split out vma_needs_dirty_tracking() from vma_wants_writenotify() to reduce duplication and update to use this in the GUP check. Note that both separately check vm_ops_needs_writenotify() as the latter needs to test this before the vm_pgprot_modify() test, resulting in vma_wants_writenotify() checking this twice, however it is such a small check this should not be egregious. https://lore.kernel.org/all/3b92d56f55671a0389252379237703df6e86ea48.1682464032.git.lstoakes@gmail.com/ v3: - Rebased on latest mm-unstable as of 24th April 2023. - Explicitly check whether file system requires folio dirtying. Note that vma_wants_writenotify() could not be used directly as it is very much focused on determining if the PTE r/w should be set (e.g. assuming private mapping does not require it as already set, soft dirty considerations). - Tested code against shmem and hugetlb mappings - confirmed that these are not disallowed by the check. - Eliminate FOLL_ALLOW_BROKEN_FILE_MAPPING flag and instead perform check only for FOLL_LONGTERM pins. - As a result, limit check to internal GUP code. https://lore.kernel.org/all/23c19e27ef0745f6d3125976e047ee0da62569d4.1682406295.git.lstoakes@gmail.com/ v2: - Add accidentally excluded ptrace_access_vm() use of FOLL_ALLOW_BROKEN_FILE_MAPPING. - Tweak commit message. https://lore.kernel.org/all/c8ee7e02d3d4f50bb3e40855c53bda39eec85b7d.1682321768.git.lstoakes@gmail.com/ v1: https://lore.kernel.org/all/f86dc089b460c80805e321747b0898fd1efe93d7.1682168199.git.lstoakes@gmail.com/ Lorenzo Stoakes (3): mm/mmap: separate writenotify and dirty tracking logic mm/gup: disallow FOLL_LONGTERM GUP-nonfast writing to file-backed mappings mm/gup: disallow FOLL_LONGTERM GUP-fast writing to file-backed mappings include/linux/mm.h | 1 + mm/gup.c | 146 ++++++++++++++++++++++++++++++++++++++++++++- mm/mmap.c | 53 ++++++++++++---- 3 files changed, 186 insertions(+), 14 deletions(-) --- 2.40.1