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 07720C7EE22 for ; Tue, 2 May 2023 17:13:57 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 664E46B0074; Tue, 2 May 2023 13:13:56 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 615376B0078; Tue, 2 May 2023 13:13:56 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 504F66B007B; Tue, 2 May 2023 13:13:56 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by kanga.kvack.org (Postfix) with ESMTP id 317B56B0074 for ; Tue, 2 May 2023 13:13:56 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1683047636; 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=tThVxt1nuGUymGM3Mj1B1ERCCnE2U7N2IjH5Ucb4/08=; b=UxWng3GUxICT8OOJix/3rOCFT/tamfdHnRe839RZ+TQp9F0JQ4jz9mC9NvPZE4NJZ//9Ub x2HPsGd4EupApBE3CAD6CygzNnmj6pD27A4l4+xx9hwRfmiJ4Gsv+ELSfvgVQ79DFqR49o ZHqlJP9IGM1F3Wh0c0vScKW4pe+27VM= Received: from mail-wr1-f70.google.com (mail-wr1-f70.google.com [209.85.221.70]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-637-QlcMIFDWPza34pqMMx2hxQ-1; Tue, 02 May 2023 13:13:53 -0400 X-MC-Unique: QlcMIFDWPza34pqMMx2hxQ-1 Received: by mail-wr1-f70.google.com with SMTP id ffacd0b85a97d-30629b36d9bso1076471f8f.0 for ; Tue, 02 May 2023 10:13:53 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683047632; x=1685639632; h=content-transfer-encoding:in-reply-to:subject:organization:from :references:cc:to:content-language:user-agent:mime-version:date :message-id:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=tThVxt1nuGUymGM3Mj1B1ERCCnE2U7N2IjH5Ucb4/08=; b=UZAVQRfKGMVZP3Bv7pP+XAvWFHK3vrA0j550XzcZKHC3JioCv+jLyEKhNr7nwjoyuh 4i7dVui7SMIRQCmJyKAeQ4e84WVnhRW0dHTzTDKFLCCLQcJBCu2i4s3y7vMW0K57Nh60 7rWTCkEXkv/RbTW+tir2ALGGBMkNqbZMYvn8kYb6JeI9qsZXdu8EnITGsbZOlYICsYnv 3Ik8Z5no/O/xNAsSdYuoiTVlmE0slf7mghiX2+ljswPfMVD1lW4rgfa5e2sWlR12x7Fz bAlnboFS8pCAHGPXB3pZRBSqen+Wcf2oVFxj1tchScuGOqaa14R+F50sg2C8ylKQ2lVl YSGA== X-Gm-Message-State: AC+VfDynw5gyCjc6/TiZdvxQQHb3HWjWPgm7W7CaFvbUBwVrkLyWLiYm bz2mP1D10BmT0aCYBivr4PGSxGzBUSpRn5Q0KyLRkefKTHbcvPxpyuXpAJ0HBuB35oX0ef2Tl02 1l6JayrCHA1s= X-Received: by 2002:adf:fe02:0:b0:2d2:29a4:4457 with SMTP id n2-20020adffe02000000b002d229a44457mr12812819wrr.13.1683047632639; Tue, 02 May 2023 10:13:52 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ5MdjSLMNym55tU5r7M2pAs93jqzP8q4u+jG7QWacNZyS3DMZ/LgP/rzfEA9/8iHAVgzgcXOg== X-Received: by 2002:adf:fe02:0:b0:2d2:29a4:4457 with SMTP id n2-20020adffe02000000b002d229a44457mr12812755wrr.13.1683047632213; Tue, 02 May 2023 10:13:52 -0700 (PDT) Received: from ?IPV6:2003:cb:c700:2400:6b79:2aa:9602:7016? (p200300cbc70024006b7902aa96027016.dip0.t-ipconnect.de. [2003:cb:c700:2400:6b79:2aa:9602:7016]) by smtp.gmail.com with ESMTPSA id q11-20020a5d574b000000b003049d7b9f4csm17477958wrw.32.2023.05.02.10.13.49 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 02 May 2023 10:13:51 -0700 (PDT) Message-ID: <1691115d-dba4-636b-d736-6a20359a67c3@redhat.com> Date: Tue, 2 May 2023 19:13:49 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0 To: Lorenzo Stoakes , 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 , Dave Chinner , Theodore Ts'o , Peter Xu , Matthew Rosato , "Paul E . McKenney" , Christian Borntraeger , Mike Rapoport References: From: David Hildenbrand Organization: Red Hat Subject: Re: [PATCH v7 3/3] mm/gup: disallow FOLL_LONGTERM GUP-fast writing to file-backed mappings In-Reply-To: X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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: [...] > +{ > + struct address_space *mapping; > + > + /* > + * GUP-fast disables IRQs - this prevents IPIs from causing page tables > + * to disappear from under us, as well as preventing RCU grace periods > + * from making progress (i.e. implying rcu_read_lock()). > + * > + * This means we can rely on the folio remaining stable for all > + * architectures, both those that set CONFIG_MMU_GATHER_RCU_TABLE_FREE > + * and those that do not. > + * > + * We get the added benefit that given inodes, and thus address_space, > + * objects are RCU freed, we can rely on the mapping remaining stable > + * here with no risk of a truncation or similar race. > + */ > + lockdep_assert_irqs_disabled(); > + > + /* > + * If no mapping can be found, this implies an anonymous or otherwise > + * non-file backed folio so in this instance we permit the pin. > + * > + * shmem and hugetlb mappings do not require dirty-tracking so we > + * explicitly whitelist these. > + * > + * Other non dirty-tracked folios will be picked up on the slow path. > + */ > + mapping = folio_mapping(folio); > + return !mapping || shmem_mapping(mapping) || folio_test_hugetlb(folio); "Folios in the swap cache return the swap mapping" -- you might disallow pinning anonymous pages that are in the swap cache. I recall that there are corner cases where we can end up with an anon page that's mapped writable but still in the swap cache ... so you'd fallback to the GUP slow path (acceptable for these corner cases, I guess), however especially the comment is a bit misleading then. So I'd suggest not dropping the folio_test_anon() check, or open-coding it ... which will make this piece of code most certainly easier to get when staring at folio_mapping(). Or to spell it out in the comment (usually I prefer code over comments). > +} > + > /** > * try_grab_folio() - Attempt to get or pin a folio. > * @page: pointer to page to be grabbed > @@ -123,6 +170,8 @@ static inline struct folio *try_get_folio(struct page *page, int refs) > */ > struct folio *try_grab_folio(struct page *page, int refs, unsigned int flags) > { > + bool is_longterm = flags & FOLL_LONGTERM; > + > if (unlikely(!(flags & FOLL_PCI_P2PDMA) && is_pci_p2pdma_page(page))) > return NULL; > > @@ -136,8 +185,7 @@ struct folio *try_grab_folio(struct page *page, int refs, unsigned int flags) > * right zone, so fail and let the caller fall back to the slow > * path. > */ > - if (unlikely((flags & FOLL_LONGTERM) && > - !is_longterm_pinnable_page(page))) > + if (unlikely(is_longterm && !is_longterm_pinnable_page(page))) > return NULL; > > /* > @@ -148,6 +196,16 @@ struct folio *try_grab_folio(struct page *page, int refs, unsigned int flags) > if (!folio) > return NULL; > > + /* > + * Can this folio be safely pinned? We need to perform this > + * check after the folio is stabilised. > + */ > + if ((flags & FOLL_WRITE) && is_longterm && > + !folio_longterm_write_pin_allowed(folio)) { > + folio_put_refs(folio, refs); > + return NULL; > + } So we perform this change before validating whether the PTE changed. Hmm, naturally, I would have done it afterwards. IIRC, without IPI syncs during TLB flush (i.e., CONFIG_MMU_GATHER_RCU_TABLE_FREE), there is the possibility that (1) We lookup the pte (2) The page was unmapped and free (3) The page gets reallocated and used (4) We pin the page (5) We dereference page->mapping If we then de-reference page->mapping that gets used by whoever allocated it for something completely different (not a pointer to something reasonable), I wonder if we might be in trouble. Checking first, whether the PTE changed makes sure that what we pinned and what we're looking at is what we expected. ... I can spot that the page_is_secretmem() check is also done before that. But it at least makes sure that it's still an LRU page before staring at the mapping (making it a little safer?). BUT, I keep messing up this part of the story. Maybe it all works as expected because we will be synchronizing RCU somehow before actually freeing the page in the !IPI case. ... but I think that's only true for page tables with CONFIG_MMU_GATHER_RCU_TABLE_FREE. -- Thanks, David / dhildenb