mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
	Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>,
	stable@vger.kernel.org,
	Rustam Subkhankulov <subkhankulov@ispras.ru>,
	xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] xen/privcmd: fix error exit of privcmd_ioctl_dm_op()
Date: Thu, 25 Aug 2022 12:13:21 +0200	[thread overview]
Message-ID: <a69d7917-daae-c8d9-5f4b-2300c99168b8@suse.com> (raw)
In-Reply-To: <2c762b15-fd7e-f14e-fcc9-a083af683e4f@suse.com>


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

On 25.08.22 11:50, Jan Beulich wrote:
> On 25.08.2022 11:26, Juergen Gross wrote:
>> 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 patches pinned by pin_user_pages_fast()
> 
> Nit: s/patches/pages/
> 
>> 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>
> 
> Reviewed-by: Jan Beulich <jbeulich@suse.com>
> 
> I have a question / suggestion, though:
> 
>> --- a/drivers/xen/privcmd.c
>> +++ b/drivers/xen/privcmd.c
>> @@ -602,6 +602,10 @@ static int lock_pages(
>>   		*pinned += page_count;
>>   		nr_pages -= page_count;
>>   		pages += page_count;
>> +
>> +		/* Exact reason isn't known, EFAULT is one possibility. */
>> +		if (page_count < requested)
>> +			return -EFAULT;
>>   	}
> 
> I don't really know the inner workings of pin_user_pages_fast()
> nor what future plans there are with it. To be as independent of
> its behavior as possible, how about bailing here only when
> page_count actually is zero (i.e. no forward progress)?

This would require to rework the loop in lock_pages() to be able to
handle only a partial buffer.

This would add some complexity, but OTOH I'd get an exact error code
back in case of failure.

I'll have a try and see how the result would look like.


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-25 10:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-25  9:26 Juergen Gross
2022-08-25  9:50 ` Jan Beulich
2022-08-25 10:13   ` Juergen Gross [this message]
2022-08-25 10:22     ` Jan Beulich
2022-08-25 11:14       ` Juergen Gross

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=a69d7917-daae-c8d9-5f4b-2300c99168b8@suse.com \
    --to=jgross@suse.com \
    --cc=jbeulich@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleksandr_tyshchenko@epam.com \
    --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

all inboxes | Powered by JetHome®