From: jgg at ziepe.ca (Jason Gunthorpe)
Subject: [PATCH v16 12/16] IB, arm64: untag user pointers in ib_uverbs_(re)reg_mr()
Date: Tue, 4 Jun 2019 10:02:07 -0300 [thread overview]
Message-ID: <20190604130207.GD15385@ziepe.ca> (raw)
In-Reply-To: <CAAeHK+xyqwuJyviGhvU7L1wPZQF7Mf9g2vgKSsYmML3fV6NrXg@mail.gmail.com>
On Tue, Jun 04, 2019 at 02:45:32PM +0200, Andrey Konovalov wrote:
> On Tue, Jun 4, 2019 at 2:27 PM Jason Gunthorpe <jgg at ziepe.ca> wrote:
> >
> > On Tue, Jun 04, 2019 at 02:18:19PM +0200, Andrey Konovalov wrote:
> > > On Mon, Jun 3, 2019 at 7:46 PM Jason Gunthorpe <jgg at ziepe.ca> wrote:
> > > >
> > > > On Mon, Jun 03, 2019 at 06:55:14PM +0200, Andrey Konovalov wrote:
> > > > > This patch is a part of a series that extends arm64 kernel ABI to allow to
> > > > > pass tagged user pointers (with the top byte set to something else other
> > > > > than 0x00) as syscall arguments.
> > > > >
> > > > > ib_uverbs_(re)reg_mr() use provided user pointers for vma lookups (through
> > > > > e.g. mlx4_get_umem_mr()), which can only by done with untagged pointers.
> > > > >
> > > > > Untag user pointers in these functions.
> > > > >
> > > > > Signed-off-by: Andrey Konovalov <andreyknvl at google.com>
> > > > > drivers/infiniband/core/uverbs_cmd.c | 4 ++++
> > > > > 1 file changed, 4 insertions(+)
> > > > >
> > > > > diff --git a/drivers/infiniband/core/uverbs_cmd.c b/drivers/infiniband/core/uverbs_cmd.c
> > > > > index 5a3a1780ceea..f88ee733e617 100644
> > > > > +++ b/drivers/infiniband/core/uverbs_cmd.c
> > > > > @@ -709,6 +709,8 @@ static int ib_uverbs_reg_mr(struct uverbs_attr_bundle *attrs)
> > > > > if (ret)
> > > > > return ret;
> > > > >
> > > > > + cmd.start = untagged_addr(cmd.start);
> > > > > +
> > > > > if ((cmd.start & ~PAGE_MASK) != (cmd.hca_va & ~PAGE_MASK))
> > > > > return -EINVAL;
> > > >
> > > > I feel like we shouldn't thave to do this here, surely the cmd.start
> > > > should flow unmodified to get_user_pages, and gup should untag it?
> > > >
> > > > ie, this sort of direction for the IB code (this would be a giant
> > > > patch, so I didn't have time to write it all, but I think it is much
> > > > saner):
> > >
> > > Hi Jason,
> > >
> > > ib_uverbs_reg_mr() passes cmd.start to mlx4_get_umem_mr(), which calls
> > > find_vma(), which only accepts untagged addresses. Could you explain
> > > how your patch helps?
> >
> > That mlx4 is just a 'weird duck', it is not the normal flow, and I
> > don't think the core code should be making special consideration for
> > it.
>
> How do you think we should do untagging (or something else) to deal
> with this 'weird duck' case?
mlx4 should handle it around the call to find_vma like other patches
do, ideally as part of the cast from a void __user * to the unsigned
long that find_vma needs
Jason
WARNING: multiple messages have this Message-ID (diff)
From: jgg@ziepe.ca (Jason Gunthorpe)
Subject: [PATCH v16 12/16] IB, arm64: untag user pointers in ib_uverbs_(re)reg_mr()
Date: Tue, 4 Jun 2019 10:02:07 -0300 [thread overview]
Message-ID: <20190604130207.GD15385@ziepe.ca> (raw)
Message-ID: <20190604130207.Ncw31XLHs1O3298PmXjywk2_KRooytGxyor0R5ZSyhk@z> (raw)
In-Reply-To: <CAAeHK+xyqwuJyviGhvU7L1wPZQF7Mf9g2vgKSsYmML3fV6NrXg@mail.gmail.com>
On Tue, Jun 04, 2019@02:45:32PM +0200, Andrey Konovalov wrote:
> On Tue, Jun 4, 2019@2:27 PM Jason Gunthorpe <jgg@ziepe.ca> wrote:
> >
> > On Tue, Jun 04, 2019@02:18:19PM +0200, Andrey Konovalov wrote:
> > > On Mon, Jun 3, 2019@7:46 PM Jason Gunthorpe <jgg@ziepe.ca> wrote:
> > > >
> > > > On Mon, Jun 03, 2019@06:55:14PM +0200, Andrey Konovalov wrote:
> > > > > This patch is a part of a series that extends arm64 kernel ABI to allow to
> > > > > pass tagged user pointers (with the top byte set to something else other
> > > > > than 0x00) as syscall arguments.
> > > > >
> > > > > ib_uverbs_(re)reg_mr() use provided user pointers for vma lookups (through
> > > > > e.g. mlx4_get_umem_mr()), which can only by done with untagged pointers.
> > > > >
> > > > > Untag user pointers in these functions.
> > > > >
> > > > > Signed-off-by: Andrey Konovalov <andreyknvl at google.com>
> > > > > drivers/infiniband/core/uverbs_cmd.c | 4 ++++
> > > > > 1 file changed, 4 insertions(+)
> > > > >
> > > > > diff --git a/drivers/infiniband/core/uverbs_cmd.c b/drivers/infiniband/core/uverbs_cmd.c
> > > > > index 5a3a1780ceea..f88ee733e617 100644
> > > > > +++ b/drivers/infiniband/core/uverbs_cmd.c
> > > > > @@ -709,6 +709,8 @@ static int ib_uverbs_reg_mr(struct uverbs_attr_bundle *attrs)
> > > > > if (ret)
> > > > > return ret;
> > > > >
> > > > > + cmd.start = untagged_addr(cmd.start);
> > > > > +
> > > > > if ((cmd.start & ~PAGE_MASK) != (cmd.hca_va & ~PAGE_MASK))
> > > > > return -EINVAL;
> > > >
> > > > I feel like we shouldn't thave to do this here, surely the cmd.start
> > > > should flow unmodified to get_user_pages, and gup should untag it?
> > > >
> > > > ie, this sort of direction for the IB code (this would be a giant
> > > > patch, so I didn't have time to write it all, but I think it is much
> > > > saner):
> > >
> > > Hi Jason,
> > >
> > > ib_uverbs_reg_mr() passes cmd.start to mlx4_get_umem_mr(), which calls
> > > find_vma(), which only accepts untagged addresses. Could you explain
> > > how your patch helps?
> >
> > That mlx4 is just a 'weird duck', it is not the normal flow, and I
> > don't think the core code should be making special consideration for
> > it.
>
> How do you think we should do untagging (or something else) to deal
> with this 'weird duck' case?
mlx4 should handle it around the call to find_vma like other patches
do, ideally as part of the cast from a void __user * to the unsigned
long that find_vma needs
Jason
next prev parent reply other threads:[~2019-06-04 13:02 UTC|newest]
Thread overview: 141+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 16:55 [PATCH v16 00/16] arm64: untag user pointers passed to the kernel andreyknvl
2019-06-03 16:55 ` Andrey Konovalov
2019-06-03 16:55 ` [PATCH v16 01/16] uaccess: add untagged_addr definition for other arches andreyknvl
2019-06-03 16:55 ` Andrey Konovalov
2019-06-03 17:02 ` khalid.aziz
2019-06-03 17:02 ` Khalid Aziz
2019-06-03 17:06 ` andreyknvl
2019-06-03 17:06 ` Andrey Konovalov
2019-06-03 17:24 ` khalid.aziz
2019-06-03 17:24 ` Khalid Aziz
2019-06-03 17:29 ` hch
2019-06-03 17:29 ` Christoph Hellwig
2019-06-03 18:17 ` khalid.aziz
2019-06-03 18:17 ` Khalid Aziz
2019-06-04 11:45 ` andreyknvl
2019-06-04 11:45 ` Andrey Konovalov
2019-06-03 16:55 ` [PATCH v16 02/16] arm64: untag user pointers in access_ok and __uaccess_mask_ptr andreyknvl
2019-06-03 16:55 ` Andrey Konovalov
2019-06-08 3:51 ` keescook
2019-06-08 3:51 ` Kees Cook
2019-06-08 3:51 ` Kees Cook
2019-06-10 17:53 ` catalin.marinas
2019-06-10 17:53 ` Catalin Marinas
2019-06-10 17:53 ` Catalin Marinas
2019-06-10 18:07 ` keescook
2019-06-10 18:07 ` Kees Cook
2019-06-10 18:07 ` Kees Cook
2019-06-10 18:53 ` catalin.marinas
2019-06-10 18:53 ` Catalin Marinas
2019-06-10 18:53 ` Catalin Marinas
2019-06-10 20:36 ` keescook
2019-06-10 20:36 ` Kees Cook
2019-06-10 20:36 ` Kees Cook
2019-06-11 14:57 ` Catalin Marinas
2019-06-11 17:09 ` Vincenzo Frascino
2019-06-12 9:32 ` Catalin Marinas
2019-06-12 11:52 ` Vincenzo Frascino
2019-06-11 17:09 ` Andrey Konovalov
2019-06-11 17:39 ` Catalin Marinas
2019-06-12 11:03 ` Andrey Konovalov
2019-06-12 11:04 ` Catalin Marinas
2019-06-03 16:55 ` [PATCH v16 03/16] lib, arm64: untag user pointers in strn*_user andreyknvl
2019-06-03 16:55 ` Andrey Konovalov
2019-06-08 3:48 ` keescook
2019-06-08 3:48 ` Kees Cook
2019-06-08 3:48 ` Kees Cook
2019-06-11 20:06 ` Khalid Aziz
2019-06-03 16:55 ` [PATCH v16 04/16] mm: untag user pointers in do_pages_move andreyknvl
2019-06-03 16:55 ` Andrey Konovalov
2019-06-08 3:49 ` keescook
2019-06-08 3:49 ` Kees Cook
2019-06-08 3:49 ` Kees Cook
2019-06-11 20:18 ` Khalid Aziz
2019-06-12 11:08 ` Andrey Konovalov
2019-06-03 16:55 ` [PATCH v16 05/16] arm64: untag user pointers passed to memory syscalls andreyknvl
2019-06-03 16:55 ` Andrey Konovalov
2019-06-08 3:51 ` keescook
2019-06-08 3:51 ` Kees Cook
2019-06-08 3:51 ` Kees Cook
2019-06-10 14:28 ` catalin.marinas
2019-06-10 14:28 ` Catalin Marinas
2019-06-10 14:28 ` Catalin Marinas
2019-06-11 15:35 ` Andrey Konovalov
2019-06-11 17:44 ` Catalin Marinas
2019-06-12 11:13 ` Andrey Konovalov
2019-06-03 16:55 ` [PATCH v16 06/16] mm, arm64: untag user pointers in mm/gup.c andreyknvl
2019-06-03 16:55 ` Andrey Konovalov
2019-06-08 3:59 ` keescook
2019-06-08 3:59 ` Kees Cook
2019-06-08 3:59 ` Kees Cook
2019-06-03 16:55 ` [PATCH v16 07/16] mm, arm64: untag user pointers in get_vaddr_frames andreyknvl
2019-06-03 16:55 ` Andrey Konovalov
2019-06-08 4:00 ` keescook
2019-06-08 4:00 ` Kees Cook
2019-06-08 4:00 ` Kees Cook
2019-06-10 14:29 ` catalin.marinas
2019-06-10 14:29 ` Catalin Marinas
2019-06-10 14:29 ` Catalin Marinas
2019-06-03 16:55 ` [PATCH v16 08/16] fs, arm64: untag user pointers in copy_mount_options andreyknvl
2019-06-03 16:55 ` Andrey Konovalov
2019-06-08 4:02 ` keescook
2019-06-08 4:02 ` Kees Cook
2019-06-08 4:02 ` Kees Cook
2019-06-11 14:38 ` Andrey Konovalov
2019-06-12 11:36 ` Andrey Konovalov
2019-06-03 16:55 ` [PATCH v16 09/16] fs, arm64: untag user pointers in fs/userfaultfd.c andreyknvl
2019-06-03 16:55 ` Andrey Konovalov
2019-06-08 4:03 ` keescook
2019-06-08 4:03 ` Kees Cook
2019-06-08 4:03 ` Kees Cook
2019-06-12 10:45 ` Catalin Marinas
2019-06-03 16:55 ` [PATCH v16 10/16] drm/amdgpu, arm64: untag user pointers andreyknvl
2019-06-03 16:55 ` Andrey Konovalov
2019-06-03 16:55 ` [PATCH v16 11/16] drm/radeon, arm64: untag user pointers in radeon_gem_userptr_ioctl andreyknvl
2019-06-03 16:55 ` Andrey Konovalov
2019-06-03 16:55 ` [PATCH v16 12/16] IB, arm64: untag user pointers in ib_uverbs_(re)reg_mr() andreyknvl
2019-06-03 16:55 ` Andrey Konovalov
2019-06-03 17:46 ` jgg
2019-06-03 17:46 ` Jason Gunthorpe
2019-06-04 12:18 ` andreyknvl
2019-06-04 12:18 ` Andrey Konovalov
2019-06-04 12:27 ` jgg
2019-06-04 12:27 ` Jason Gunthorpe
2019-06-04 12:45 ` andreyknvl
2019-06-04 12:45 ` Andrey Konovalov
2019-06-04 13:02 ` jgg [this message]
2019-06-04 13:02 ` Jason Gunthorpe
2019-06-04 13:09 ` andreyknvl
2019-06-04 13:09 ` Andrey Konovalov
2019-06-12 11:01 ` Catalin Marinas
2019-06-03 16:55 ` [PATCH v16 13/16] media/v4l2-core, arm64: untag user pointers in videobuf_dma_contig_user_get andreyknvl
2019-06-03 16:55 ` Andrey Konovalov
2019-06-08 3:52 ` keescook
2019-06-08 3:52 ` Kees Cook
2019-06-08 3:52 ` Kees Cook
2019-06-03 16:55 ` [PATCH v16 14/16] tee, arm64: untag user pointers in tee_shm_register andreyknvl
2019-06-03 16:55 ` Andrey Konovalov
2019-06-07 5:33 ` jens.wiklander
2019-06-07 5:33 ` Jens Wiklander
2019-06-07 5:33 ` Jens Wiklander
2019-06-08 4:05 ` keescook
2019-06-08 4:05 ` Kees Cook
2019-06-08 4:05 ` Kees Cook
2019-06-03 16:55 ` [PATCH v16 15/16] vfio/type1, arm64: untag user pointers in vaddr_get_pfn andreyknvl
2019-06-03 16:55 ` Andrey Konovalov
2019-06-08 3:58 ` keescook
2019-06-08 3:58 ` Kees Cook
2019-06-08 3:58 ` Kees Cook
2019-06-12 10:38 ` Catalin Marinas
2019-06-03 16:55 ` [PATCH v16 16/16] selftests, arm64: add a selftest for passing tagged pointers to kernel andreyknvl
2019-06-03 16:55 ` Andrey Konovalov
2019-06-08 3:56 ` keescook
2019-06-08 3:56 ` Kees Cook
2019-06-08 3:56 ` Kees Cook
2019-06-10 22:08 ` shuah
2019-06-10 22:08 ` shuah
2019-06-10 22:08 ` shuah
2019-06-11 15:01 ` Catalin Marinas
2019-06-11 17:18 ` Andrey Konovalov
2019-06-11 17:50 ` Catalin Marinas
2019-06-12 11:14 ` Andrey Konovalov
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=20190604130207.GD15385@ziepe.ca \
--to=linux-kselftest@vger.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