From: Jason Gunthorpe <jgg@nvidia.com>
To: Claudio Imbrenda <imbrenda@linux.ibm.com>
Cc: David Hildenbrand <david@redhat.com>,
Alistair Popple <apopple@nvidia.com>,
David Howells <dhowells@redhat.com>,
Christoph Hellwig <hch@infradead.org>,
John Hubbard <jhubbard@nvidia.com>,
linux-mm@kvack.org, "Mike Rapoport (IBM)" <rppt@kernel.org>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Janosch Frank <frankja@linux.ibm.com>
Subject: Re: [PATCH v2 13/13] mm/gup: move private gup FOLL_ flags to internal.h
Date: Mon, 30 Jan 2023 14:24:40 -0400 [thread overview]
Message-ID: <Y9gLaAKYjVY3e4lc@nvidia.com> (raw)
In-Reply-To: <20230130192104.41c5b426@p-imbrenda>
On Mon, Jan 30, 2023 at 07:21:04PM +0100, Claudio Imbrenda wrote:
> On Thu, 26 Jan 2023 12:35:37 -0400
> Jason Gunthorpe <jgg@nvidia.com> wrote:
>
> > On Thu, Jan 26, 2023 at 04:39:02PM +0100, Claudio Imbrenda wrote:
> >
> > > I can tell you that the original goal of that function is to make sure
> > > that there are no extra references. in particular, we want to prevent
> > > I/O of any kind to be ongoing while the page becomes secure. (the I/O
> > > will fail and, depending on which device it was, the whole system might
> > > end up in a rather unhappy state)
> >
> > Sure, but if there is concurrent IO you just try again right? It
> > doesn't wait for refs to drop for instance.
> >
> > So make the lock_page work the same way:
>
> the more I look at this, the less I understand why I wrote the code
> like that. I do have a comment, though
>
> >
> > diff --git a/arch/s390/kernel/uv.c b/arch/s390/kernel/uv.c
> > index 9f18a4af9c1319..847ee50b8672c6 100644
> > --- a/arch/s390/kernel/uv.c
> > +++ b/arch/s390/kernel/uv.c
> > @@ -193,20 +193,11 @@ static int expected_page_refs(struct page *page)
> > }
> >
> > static int make_secure_pte(pte_t *ptep, unsigned long addr,
> > - struct page *exp_page, struct uv_cb_header *uvcb)
> > + struct page *page, struct uv_cb_header *uvcb)
> > {
> > pte_t entry = READ_ONCE(*ptep);
> > - struct page *page;
> > int expected, cc = 0;
> >
> > - if (!pte_present(entry))
> > - return -ENXIO;
> > - if (pte_val(entry) & _PAGE_INVALID)
> > - return -ENXIO;
> > -
> > - page = pte_page(entry);
> > - if (page != exp_page)
> > - return -ENXIO;
> > if (PageWriteback(page))
> > return -EAGAIN;
> > expected = expected_page_refs(page);
> > @@ -304,17 +295,25 @@ int gmap_make_secure(struct gmap *gmap, unsigned long gaddr, void *uvcb)
> > goto out;
> >
> > rc = -ENXIO;
> > - page = follow_page(vma, uaddr, FOLL_WRITE);
> > - if (IS_ERR_OR_NULL(page))
> > - goto out;
> > -
> > - lock_page(page);
> > ptep = get_locked_pte(gmap->mm, uaddr, &ptelock);
> > +
> > + if (!pte_present(entry))
> > + goto out_unlock_pte;
> > + if (pte_val(entry) & _PAGE_INVALID)
> > + goto out_unlock_pte;
>
> I guess we also need to make sure the page was writable?
> FOLL_WRITE made sure of that
>
> so I guess something like:
>
> if (!pte_write(entry))
> goto out_unlock_pte;
Probably, that looks like an existing race that it wasn't re-checked :\
Jason
next prev parent reply other threads:[~2023-01-30 18:24 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 20:34 [PATCH v2 00/13] Simplify the external interface for GUP Jason Gunthorpe
2023-01-24 20:34 ` [PATCH v2 01/13] mm/gup: have internal functions get the mmap_read_lock() Jason Gunthorpe
2023-01-25 2:11 ` John Hubbard
2023-01-25 2:52 ` John Hubbard
2023-01-25 16:38 ` Jason Gunthorpe
2023-01-25 18:48 ` John Hubbard
2023-01-24 20:34 ` [PATCH v2 02/13] mm/gup: remove obsolete FOLL_LONGTERM comment Jason Gunthorpe
2023-01-25 2:13 ` John Hubbard
2023-02-08 14:25 ` David Hildenbrand
2023-01-24 20:34 ` [PATCH v2 03/13] mm/gup: don't call __gup_longterm_locked() if FOLL_LONGTERM cannot be set Jason Gunthorpe
2023-02-08 14:26 ` David Hildenbrand
2023-01-24 20:34 ` [PATCH v2 04/13] mm/gup: move try_grab_page() to mm/internal.h Jason Gunthorpe
2023-01-25 2:15 ` John Hubbard
2023-02-08 14:26 ` David Hildenbrand
2023-01-24 20:34 ` [PATCH v2 05/13] mm/gup: simplify the external interface functions and consolidate invariants Jason Gunthorpe
2023-01-25 2:30 ` John Hubbard
2023-01-24 20:34 ` [PATCH v2 06/13] mm/gup: add an assertion that the mmap lock is locked Jason Gunthorpe
2023-01-25 2:34 ` John Hubbard
2023-01-24 20:34 ` [PATCH v2 07/13] mm/gup: remove locked being NULL from faultin_vma_page_range() Jason Gunthorpe
2023-01-25 2:38 ` John Hubbard
2023-01-24 20:34 ` [PATCH v2 08/13] mm/gup: add FOLL_UNLOCKABLE Jason Gunthorpe
2023-01-24 20:34 ` [PATCH v2 09/13] mm/gup: make locked never NULL in the internal GUP functions Jason Gunthorpe
2023-01-25 3:00 ` John Hubbard
2023-01-24 20:34 ` [PATCH v2 10/13] mm/gup: remove pin_user_pages_fast_only() Jason Gunthorpe
2023-01-24 20:34 ` [PATCH v2 11/13] mm/gup: make get_user_pages_fast_only() return the common return value Jason Gunthorpe
2023-01-24 20:34 ` [PATCH v2 12/13] mm/gup: move gup_must_unshare() to mm/internal.h Jason Gunthorpe
2023-01-25 2:41 ` John Hubbard
2023-01-26 11:29 ` David Hildenbrand
2023-01-24 20:34 ` [PATCH v2 13/13] mm/gup: move private gup FOLL_ flags to internal.h Jason Gunthorpe
2023-01-25 2:44 ` John Hubbard
2023-01-26 12:48 ` David Hildenbrand
2023-01-26 12:55 ` Jason Gunthorpe
2023-01-26 13:06 ` David Hildenbrand
2023-01-26 14:41 ` Claudio Imbrenda
2023-01-26 14:46 ` David Hildenbrand
2023-01-26 15:05 ` Jason Gunthorpe
2023-01-26 15:39 ` Claudio Imbrenda
2023-01-26 16:35 ` Jason Gunthorpe
2023-01-26 17:24 ` Claudio Imbrenda
2023-01-30 18:21 ` Claudio Imbrenda
2023-01-30 18:24 ` Jason Gunthorpe [this message]
2023-02-07 11:31 ` Claudio Imbrenda
2023-02-07 12:40 ` Jason Gunthorpe
2023-02-06 23:46 ` [PATCH v2 00/13] Simplify the external interface for GUP Jason Gunthorpe
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=Y9gLaAKYjVY3e4lc@nvidia.com \
--to=jgg@nvidia.com \
--cc=apopple@nvidia.com \
--cc=borntraeger@linux.ibm.com \
--cc=david@redhat.com \
--cc=dhowells@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=hch@infradead.org \
--cc=imbrenda@linux.ibm.com \
--cc=jhubbard@nvidia.com \
--cc=linux-mm@kvack.org \
--cc=rppt@kernel.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