The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: Oleksandr Tyshchenko <Oleksandr_Tyshchenko@epam.com>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	Rustam Subkhankulov <subkhankulov@ispras.ru>
Subject: Re: [PATCH v4] xen/privcmd: fix error exit of privcmd_ioctl_dm_op()
Date: Fri, 26 Aug 2022 11:29:05 +0200	[thread overview]
Message-ID: <df018a26-d81b-7785-6deb-1721cf7f4530@suse.com> (raw)
In-Reply-To: <5e749d5e-08d9-81c9-0f46-a06be2d752ce@epam.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 3514 bytes --]

On 26.08.22 11:08, Oleksandr Tyshchenko wrote:
> 
> On 25.08.22 17:19, Juergen Gross wrote:
> 
> Hello Juergen
> 
>> The error exit of privcmd_ioctl_dm_op() is calling unlock_pages()
>> potentially with pages being NULL, leading to a NULL dereference.
>>
>> Additionally lock_pages() doesn't check for pin_user_pages_fast()
>> having been completely successful, resulting in potentially not
>> locking all pages into memory. This could result in sporadic failures
>> when using the related memory in user mode.
>>
>> Fix all of that by calling unlock_pages() always with the real number
>> of pinned pages, which will be zero in case pages being NULL, and by
>> checking the number of pages pinned by pin_user_pages_fast() matching
>> the expected number of pages.
>>
>> Cc: <stable@vger.kernel.org>
>> Fixes: ab520be8cd5d ("xen/privcmd: Add IOCTL_PRIVCMD_DM_OP")
>> Reported-by: Rustam Subkhankulov <subkhankulov@ispras.ru>
>> Signed-off-by: Juergen Gross <jgross@suse.com>
> 
> 
> I haven't spotted any issues:
> 
> Reviewed-by: Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>
> 
> 
>> ---
>> V2:
>> - use "pinned" as parameter for unlock_pages() (Jan Beulich)
>> - drop label "unlock" again (Jan Beulich)
>> - add check for complete success of pin_user_pages_fast()
>> V3:
>> - continue after partial success of pin_user_pages_fast() (Jan Beulich)
>> V4:
>> - fix case of multiple partial successes for one buffer (Jan Beulich)
>> ---
>>    drivers/xen/privcmd.c | 21 +++++++++++----------
>>    1 file changed, 11 insertions(+), 10 deletions(-)
>>
>> diff --git a/drivers/xen/privcmd.c b/drivers/xen/privcmd.c
>> index 3369734108af..e88e8f6f0a33 100644
>> --- a/drivers/xen/privcmd.c
>> +++ b/drivers/xen/privcmd.c
>> @@ -581,27 +581,30 @@ static int lock_pages(
>>    	struct privcmd_dm_op_buf kbufs[], unsigned int num,
>>    	struct page *pages[], unsigned int nr_pages, unsigned int *pinned)
>>    {
>> -	unsigned int i;
>> +	unsigned int i, off = 0;
>>    
>> -	for (i = 0; i < num; i++) {
>> +	for (i = 0; i < num; ) {
>>    		unsigned int requested;
>>    		int page_count;
>>    
>>    		requested = DIV_ROUND_UP(
>>    			offset_in_page(kbufs[i].uptr) + kbufs[i].size,
>> -			PAGE_SIZE);
>> +			PAGE_SIZE) - off;
>>    		if (requested > nr_pages)
>>    			return -ENOSPC;
>>    
>>    		page_count = pin_user_pages_fast(
>> -			(unsigned long) kbufs[i].uptr,
>> +			(unsigned long)kbufs[i].uptr + off * PAGE_SIZE,
>>    			requested, FOLL_WRITE, pages);
>> -		if (page_count < 0)
>> -			return page_count;
>> +		if (page_count <= 0)
>> +			return page_count ? : -EFAULT;
> 
> 
> [not related to the current patch]
> 
> I just wonder, whether drivers/xen/gntdev.c:gntdev_get_page() really
> wants to gain the same check?
> 
> index 59ffea800079..45e16031204d 100644
> --- a/drivers/xen/gntdev.c
> +++ b/drivers/xen/gntdev.c
> @@ -740,8 +740,8 @@ static int gntdev_get_page(struct gntdev_copy_batch
> *batch, void __user *virt,
>           int ret;
> 
>           ret = pin_user_pages_fast(addr, 1, batch->writeable ?
> FOLL_WRITE : 0, &page);
> -       if (ret < 0)
> -               return ret;
> +       if (ret <= 0)
> +               return ret ? : -EFAULT;
> 
>           batch->pages[batch->nr_pages++] = page;

I don't think this is needed here, as pin_user_pages_fast() can't
return 0 when called for a single page.


Juergen

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3149 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

      reply	other threads:[~2022-08-26  9:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-25 14:19 [PATCH v4] xen/privcmd: fix error exit of privcmd_ioctl_dm_op() Juergen Gross
2022-08-25 14:37 ` Jan Beulich
2022-08-26  9:08 ` Oleksandr Tyshchenko
2022-08-26  9:29   ` Juergen Gross [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=df018a26-d81b-7785-6deb-1721cf7f4530@suse.com \
    --to=jgross@suse.com \
    --cc=Oleksandr_Tyshchenko@epam.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sstabellini@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=subkhankulov@ispras.ru \
    --cc=xen-devel@lists.xenproject.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