From: David Hildenbrand <david@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>,
Lorenzo Stoakes <lstoakes@gmail.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Jason Gunthorpe <jgg@ziepe.ca>, Jens Axboe <axboe@kernel.dk>,
Matthew Wilcox <willy@infradead.org>,
Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>,
Leon Romanovsky <leon@kernel.org>,
Christian Benvenuti <benve@cisco.com>,
Nelson Escobar <neescoba@cisco.com>,
Bernard Metzler <bmt@zurich.ibm.com>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Bjorn Topel <bjorn@kernel.org>,
Magnus Karlsson <magnus.karlsson@intel.com>,
Maciej Fijalkowski <maciej.fijalkowski@intel.com>,
Jonathan Lemon <jonathan.lemon@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Christian Brauner <brauner@kernel.org>,
Richard Cochran <richardcochran@gmail.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Jesper Dangaard Brouer <hawk@kernel.org>,
John Fastabend <john.fastabend@gmail.com>,
linux-fsdevel@vger.kernel.org, linux-perf-users@vger.kernel.org,
netdev@vger.kernel.org, bpf@vger.kernel.org,
Oleg Nesterov <oleg@redhat.com>, Jason Gunthorpe <jgg@nvidia.com>,
John Hubbard <jhubbard@nvidia.com>, Jan Kara <jack@suse.cz>,
"Kirill A . Shutemov" <kirill@shutemov.name>,
Pavel Begunkov <asml.silence@gmail.com>,
Mika Penttila <mpenttil@redhat.com>,
Dave Chinner <david@fromorbit.com>, Theodore Ts'o <tytso@mit.edu>,
Peter Xu <peterx@redhat.com>, Paul McKenney <paulmck@kernel.org>
Subject: Re: [PATCH v6 3/3] mm/gup: disallow FOLL_LONGTERM GUP-fast writing to file-backed mappings
Date: Tue, 2 May 2023 14:47:22 +0200 [thread overview]
Message-ID: <a597947b-6aba-bd8d-7a97-582fa7f88ad2@redhat.com> (raw)
In-Reply-To: <20230502124058.GB1597602@hirez.programming.kicks-ass.net>
On 02.05.23 14:40, Peter Zijlstra wrote:
> On Tue, May 02, 2023 at 02:08:10PM +0200, Peter Zijlstra wrote:
>
>>>>
>>>>
>>>> if (folio_test_anon(folio))
>>>> return true;
>>>
>>> This relies on the mapping so belongs below the lockdep assert imo.
>>
>> Oh, right you are.
>>
>>>>
>>>> /*
>>>> * Having IRQs disabled (as per GUP-fast) also inhibits RCU
>>>> * grace periods from making progress, IOW. they imply
>>>> * rcu_read_lock().
>>>> */
>>>> lockdep_assert_irqs_disabled();
>>>>
>>>> /*
>>>> * Inodes and thus address_space are RCU freed and thus safe to
>>>> * access at this point.
>>>> */
>>>> mapping = folio_mapping(folio);
>>>> if (mapping && shmem_mapping(mapping))
>>>> return true;
>>>>
>>>> return false;
>>>>
>>>>> +}
>
> So arguably you should do *one* READ_ONCE() load of mapping and
> consistently use that, this means open-coding both folio_test_anon() and
> folio_mapping().
Open-coding folio_test_anon() should not be required. We only care about
PAGE_MAPPING_FLAGS stored alongside folio->mapping, that will stick
around until the anon page was freed.
@Lorenzo, you might also want to special-case hugetlb directly using
folio_test_hugetlb().
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2023-05-02 12:48 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-01 23:11 [PATCH v6 0/3] mm/gup: disallow GUP writing to file-backed mappings by default Lorenzo Stoakes
2023-05-01 23:11 ` [PATCH v6 1/3] mm/mmap: separate writenotify and dirty tracking logic Lorenzo Stoakes
2023-05-01 23:11 ` [PATCH v6 2/3] mm/gup: disallow FOLL_LONGTERM GUP-nonfast writing to file-backed mappings Lorenzo Stoakes
2023-05-02 15:04 ` David Hildenbrand
2023-05-02 15:17 ` Lorenzo Stoakes
2023-05-01 23:11 ` [PATCH v6 3/3] mm/gup: disallow FOLL_LONGTERM GUP-fast " Lorenzo Stoakes
2023-05-01 23:42 ` John Hubbard
2023-05-02 11:13 ` Peter Zijlstra
2023-05-02 11:23 ` Jan Kara
2023-05-02 11:25 ` Lorenzo Stoakes
2023-05-02 11:28 ` Lorenzo Stoakes
2023-05-02 12:08 ` Peter Zijlstra
2023-05-02 12:27 ` Lorenzo Stoakes
2023-05-02 12:40 ` Peter Zijlstra
2023-05-02 12:47 ` David Hildenbrand [this message]
2023-05-02 12:52 ` Lorenzo Stoakes
2023-05-02 12:53 ` David Hildenbrand
2023-05-02 13:30 ` Paul E. McKenney
2023-05-02 11:20 ` Jan Kara
2023-05-02 12:46 ` Christian Borntraeger
2023-05-02 12:54 ` Lorenzo Stoakes
2023-05-02 13:02 ` Jason Gunthorpe
2023-05-02 13:04 ` Christian Borntraeger
2023-05-02 13:10 ` Jason Gunthorpe
2023-05-02 13:28 ` David Hildenbrand
2023-05-02 13:36 ` Jason Gunthorpe
2023-05-02 13:39 ` David Hildenbrand
2023-05-02 13:43 ` Matthew Rosato
2023-05-02 13:47 ` David Hildenbrand
2023-05-02 13:50 ` Jason Gunthorpe
2023-05-02 13:56 ` Matthew Rosato
2023-05-02 15:09 ` David Hildenbrand
2023-05-02 15:19 ` Lorenzo Stoakes
2023-05-02 15:20 ` Matthew Rosato
2023-05-02 13:57 ` David Hildenbrand
2023-05-02 14:04 ` Jason Gunthorpe
2023-05-02 14:15 ` David Hildenbrand
2023-05-02 14:54 ` Matthew Rosato
2023-05-02 15:20 ` Jason Gunthorpe
2023-05-02 15:32 ` Peter Xu
2023-05-02 15:36 ` Jason Gunthorpe
2023-05-02 15:45 ` David Hildenbrand
2023-05-02 16:06 ` Jason Gunthorpe
2023-05-02 16:12 ` David Hildenbrand
2023-05-02 16:19 ` Jason Gunthorpe
2023-05-02 16:32 ` David Hildenbrand
2023-05-02 17:46 ` Jason Gunthorpe
2023-05-02 17:59 ` Matthew Rosato
2023-05-02 18:09 ` Jason Gunthorpe
2023-05-02 19:23 ` David Hildenbrand
2023-05-02 13:38 ` Matthew Rosato
2023-05-02 13:35 ` Matthew Rosato
2023-05-02 14:57 ` David Hildenbrand
2023-05-02 15:19 ` Matthew Rosato
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a597947b-6aba-bd8d-7a97-582fa7f88ad2@redhat.com \
--to=david@redhat.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=asml.silence@gmail.com \
--cc=ast@kernel.org \
--cc=axboe@kernel.dk \
--cc=benve@cisco.com \
--cc=bjorn@kernel.org \
--cc=bmt@zurich.ibm.com \
--cc=bpf@vger.kernel.org \
--cc=brauner@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=david@fromorbit.com \
--cc=dennis.dalessandro@cornelisnetworks.com \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=irogers@google.com \
--cc=jack@suse.cz \
--cc=jgg@nvidia.com \
--cc=jgg@ziepe.ca \
--cc=jhubbard@nvidia.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=jonathan.lemon@gmail.com \
--cc=kirill@shutemov.name \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=lstoakes@gmail.com \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@intel.com \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=mpenttil@redhat.com \
--cc=namhyung@kernel.org \
--cc=neescoba@cisco.com \
--cc=netdev@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=pabeni@redhat.com \
--cc=paulmck@kernel.org \
--cc=peterx@redhat.com \
--cc=peterz@infradead.org \
--cc=richardcochran@gmail.com \
--cc=tytso@mit.edu \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).