From: Matthew Wilcox <willy@infradead.org>
To: John Hubbard <jhubbard@nvidia.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrea Arcangeli <aarcange@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux-MM <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Yu Zhao <yuzhao@google.com>, Andy Lutomirski <luto@kernel.org>,
Peter Xu <peterx@redhat.com>, Pavel Emelyanov <xemul@openvz.org>,
Mike Kravetz <mike.kravetz@oracle.com>,
Mike Rapoport <rppt@linux.vnet.ibm.com>,
Minchan Kim <minchan@kernel.org>, Will Deacon <will@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Hugh Dickins <hughd@google.com>,
"Kirill A. Shutemov" <kirill@shutemov.name>,
Oleg Nesterov <oleg@redhat.com>, Jann Horn <jannh@google.com>,
Kees Cook <keescook@chromium.org>,
Leon Romanovsky <leonro@nvidia.com>,
Jason Gunthorpe <jgg@ziepe.ca>, Jan Kara <jack@suse.cz>,
Kirill Tkhai <ktkhai@virtuozzo.com>,
Nadav Amit <nadav.amit@gmail.com>, Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH 0/1] mm: restore full accuracy in COW page reuse
Date: Mon, 11 Jan 2021 12:42:20 +0000 [thread overview]
Message-ID: <20210111124220.GE35215@casper.infradead.org> (raw)
In-Reply-To: <45806a5a-65c2-67ce-fc92-dc8c2144d766@nvidia.com>
On Sun, Jan 10, 2021 at 11:26:57PM -0800, John Hubbard wrote:
> IMHO, a lot of the bits in page _refcount are still being wasted (even
> after GUP_PIN_COUNTING_BIAS overloading), because it's unlikely that
> there are many callers of gup/pup per page. If anyone points out that
> that is wrong, then the rest of this falls apart, but...if we were to
> make a rule that "only a very few FOLL_GET or FOLL_PIN pins are ever
> simultaneously allowed on a given page", then several things become
> possible:
There's "the normal case" and then there's "the attacker case" where
someone's deliberately trying to wrap page->_refcount. There are lots of
interesting games people can play with an anon page, like stuffing it into
(lots of) pipes, forking lots of children, starting lots of O_DIRECT I/O
against it to a FUSE filesystem that's deliberately engineered to be slow.
We have some protection against that, but I'm not 100% sure it's working,
and making it easier to increase refcount in large chunks makes it more
likely that we would defeat that protection.
next prev parent reply other threads:[~2021-01-11 12:43 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-10 0:44 [PATCH 0/1] mm: restore full accuracy in COW page reuse Andrea Arcangeli
2021-01-10 0:44 ` [PATCH 1/1] " Andrea Arcangeli
2021-01-10 2:54 ` Andrea Arcangeli
2021-01-11 14:11 ` Kirill A. Shutemov
2021-01-10 0:55 ` [PATCH 0/1] " Linus Torvalds
2021-01-10 1:19 ` Linus Torvalds
2021-01-10 1:37 ` Linus Torvalds
2021-01-10 3:24 ` Andrea Arcangeli
2021-01-10 2:51 ` Andrea Arcangeli
2021-01-10 3:51 ` Linus Torvalds
2021-01-10 19:30 ` Linus Torvalds
2021-01-11 1:18 ` Jason Gunthorpe
2021-01-11 7:26 ` John Hubbard
2021-01-11 12:42 ` Matthew Wilcox [this message]
2021-01-11 16:05 ` Jason Gunthorpe
2021-01-11 16:15 ` Michal Hocko
2021-01-11 19:19 ` Linus Torvalds
2021-01-11 22:18 ` Linus Torvalds
2021-01-12 17:07 ` Andy Lutomirski
2021-01-12 23:51 ` Jerome Glisse
2021-01-13 2:16 ` Matthew Wilcox
2021-01-13 2:43 ` Linus Torvalds
2021-01-13 3:31 ` Linus Torvalds
2021-01-13 8:52 ` David Hildenbrand
2021-01-13 8:57 ` David Hildenbrand
2021-01-13 12:32 ` Kirill A. Shutemov
2021-01-13 12:55 ` Matthew Wilcox
2021-01-13 19:54 ` Linus Torvalds
2021-01-13 23:54 ` Peter Xu
2021-01-11 15:52 ` Jason Gunthorpe
2021-01-15 8:59 ` David Hildenbrand
2021-01-15 18:37 ` Jason Gunthorpe
2021-01-15 19:46 ` David Hildenbrand
2021-01-15 19:53 ` Jason Gunthorpe
2021-01-16 3:40 ` John Hubbard
2021-01-16 11:42 ` David Hildenbrand
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=20210111124220.GE35215@casper.infradead.org \
--to=willy@infradead.org \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=hughd@google.com \
--cc=jack@suse.cz \
--cc=jannh@google.com \
--cc=jgg@ziepe.ca \
--cc=jhubbard@nvidia.com \
--cc=keescook@chromium.org \
--cc=kirill@shutemov.name \
--cc=ktkhai@virtuozzo.com \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mike.kravetz@oracle.com \
--cc=minchan@kernel.org \
--cc=nadav.amit@gmail.com \
--cc=oleg@redhat.com \
--cc=peterx@redhat.com \
--cc=peterz@infradead.org \
--cc=rppt@linux.vnet.ibm.com \
--cc=torvalds@linux-foundation.org \
--cc=will@kernel.org \
--cc=xemul@openvz.org \
--cc=yuzhao@google.com \
/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).