All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paraschiv, Andra-Irina" <andraprs@amazon.com>
To: Vitaly Kuznetsov <vkuznets@redhat.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Greg KH <gregkh@linuxfoundation.org>
Cc: Alexandru Ciobotaru <alcioa@amazon.com>,
	Alexandru Vasile <lexnv@amazon.com>,
	Marcelo Cerri <marcelo.cerri@canonical.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	Stefano Garzarella <sgarzare@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Tim Gardner <tim.gardner@canonical.com>,
	kvm <kvm@vger.kernel.org>,
	ne-devel-upstream <ne-devel-upstream@amazon.com>,
	stable <stable@vger.kernel.org>
Subject: Re: [PATCH v1 ] nitro_enclaves: Add mmap_read_lock() for the get_user_pages() call
Date: Mon, 20 Dec 2021 22:04:27 +0200	[thread overview]
Message-ID: <0aa6bada-be03-a5bb-2ba6-57536c42276c@amazon.com> (raw)
In-Reply-To: <87o85btyso.fsf@redhat.com>



On 20.12.2021 11:23, Vitaly Kuznetsov wrote:
> 
> Andra Paraschiv <andraprs@amazon.com> writes:
> 
>> After commit 5b78ed24e8ec (mm/pagemap: add mmap_assert_locked()
>> annotations to find_vma*()), the call to get_user_pages() will trigger
>> the mmap assert.
>>
>> static inline void mmap_assert_locked(struct mm_struct *mm)
>> {
>>        lockdep_assert_held(&mm->mmap_lock);
>>        VM_BUG_ON_MM(!rwsem_is_locked(&mm->mmap_lock), mm);
>> }
>>
>> [   62.521410] kernel BUG at include/linux/mmap_lock.h:156!
>> ...........................................................
>> [   62.538938] RIP: 0010:find_vma+0x32/0x80
>> ...........................................................
>> [   62.605889] Call Trace:
>> [   62.608502]  <TASK>
>> [   62.610956]  ? lock_timer_base+0x61/0x80
>> [   62.614106]  find_extend_vma+0x19/0x80
>> [   62.617195]  __get_user_pages+0x9b/0x6a0
>> [   62.620356]  __gup_longterm_locked+0x42d/0x450
>> [   62.623721]  ? finish_wait+0x41/0x80
>> [   62.626748]  ? __kmalloc+0x178/0x2f0
>> [   62.629768]  ne_set_user_memory_region_ioctl.isra.0+0x225/0x6a0 [nitro_enclaves]
>> [   62.635776]  ne_enclave_ioctl+0x1cf/0x6d7 [nitro_enclaves]
>> [   62.639541]  __x64_sys_ioctl+0x82/0xb0
>> [   62.642620]  do_syscall_64+0x3b/0x90
>> [   62.645642]  entry_SYSCALL_64_after_hwframe+0x44/0xae
>>
>> Add mmap_read_lock() for the get_user_pages() call when setting the
>> enclave memory regions.
>>
>> Signed-off-by: Andra Paraschiv <andraprs@amazon.com>
>> Cc: stable@vger.kernel.org
> 
> In case commit 5b78ed24e8ec broke Nitro Enclaves driver, we need to
> explicitly state this:
> 
> Fixes: 5b78ed24e8ec ("mm/pagemap: add mmap_assert_locked() annotations to find_vma*()")

Added to the commit message.

> 
>> ---
>>   drivers/virt/nitro_enclaves/ne_misc_dev.c | 5 +++++
>>   1 file changed, 5 insertions(+)
>>
>> diff --git a/drivers/virt/nitro_enclaves/ne_misc_dev.c b/drivers/virt/nitro_enclaves/ne_misc_dev.c
>> index 8939612ee0e0..6c51ff024036 100644
>> --- a/drivers/virt/nitro_enclaves/ne_misc_dev.c
>> +++ b/drivers/virt/nitro_enclaves/ne_misc_dev.c
>> @@ -886,8 +886,13 @@ static int ne_set_user_memory_region_ioctl(struct ne_enclave *ne_enclave,
>>                        goto put_pages;
>>                }
>>
>> +             mmap_read_lock(current->mm);
>> +
>>                gup_rc = get_user_pages(mem_region.userspace_addr + memory_size, 1, FOLL_GET,
>>                                        ne_mem_region->pages + i, NULL);
>> +
>> +             mmap_read_unlock(current->mm);
>> +
> 
> This looks very much like get_user_pages_unlocked(), I think we can use
> it instead of open-coding it.

Indeed, it's mentioned as well in the comment for 
get_user_pages_unlocked() this pattern of mmap_read_lock() / 
get_user_pages() / mmap_read_unlock().

Thank you for the feedback, Vitaly. I sent v2 that includes the 
mentioned updates.

Thanks,
Andra


> 
>>                if (gup_rc < 0) {
>>                        rc = gup_rc;
> 
> --
> Vitaly
> 



Amazon Development Center (Romania) S.R.L. registered office: 27A Sf. Lazar Street, UBC5, floor 2, Iasi, Iasi County, 700045, Romania. Registered in Romania. Registration number J22/2621/2005.

      reply	other threads:[~2021-12-20 20:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-18 10:35 [PATCH v1 ] nitro_enclaves: Add mmap_read_lock() for the get_user_pages() call Andra Paraschiv
2021-12-18 10:43 ` Paraschiv, Andra-Irina
2022-01-03 15:03   ` Paraschiv, Andra-Irina
2021-12-20  9:23 ` Vitaly Kuznetsov
2021-12-20 20:04   ` Paraschiv, Andra-Irina [this message]

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=0aa6bada-be03-a5bb-2ba6-57536c42276c@amazon.com \
    --to=andraprs@amazon.com \
    --cc=alcioa@amazon.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kvm@vger.kernel.org \
    --cc=lexnv@amazon.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.cerri@canonical.com \
    --cc=ne-devel-upstream@amazon.com \
    --cc=pbonzini@redhat.com \
    --cc=sgarzare@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=stefanha@redhat.com \
    --cc=tim.gardner@canonical.com \
    --cc=vkuznets@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.