netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: kvm@vger.kernel.org, virtualization@lists.linux-foundation.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] vhost-vdpa: honor CAP_IPC_LOCK
Date: Tue, 2 Mar 2021 18:52:27 +0800	[thread overview]
Message-ID: <4f3dcc1e-b95d-f17c-b371-52119d693d10@redhat.com> (raw)
In-Reply-To: <20210302044918-mutt-send-email-mst@kernel.org>


On 2021/3/2 5:51 下午, Michael S. Tsirkin wrote:
> On Tue, Mar 02, 2021 at 04:14:18AM -0500, Jason Wang wrote:
>> When CAP_IPC_LOCK is set we should not check locked memory against
>> rlimit as what has been implemented in mlock().
>>
>> Signed-off-by: Jason Wang <jasowang@redhat.com>
> Indeed and it's not just mlock.
>
> Documentation/admin-guide/perf-security.rst:
>
> RLIMIT_MEMLOCK and perf_event_mlock_kb resource constraints are ignored
> for processes with the CAP_IPC_LOCK capability.
>
> and let's add a Fixes: tag?


Sure, V2 is posted.

Thanks


>
>> ---
>>   drivers/vhost/vdpa.c | 3 ++-
>>   1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/vhost/vdpa.c b/drivers/vhost/vdpa.c
>> index ef688c8c0e0e..e93572e2e344 100644
>> --- a/drivers/vhost/vdpa.c
>> +++ b/drivers/vhost/vdpa.c
>> @@ -638,7 +638,8 @@ static int vhost_vdpa_process_iotlb_update(struct vhost_vdpa *v,
>>   	mmap_read_lock(dev->mm);
>>   
>>   	lock_limit = rlimit(RLIMIT_MEMLOCK) >> PAGE_SHIFT;
>> -	if (npages + atomic64_read(&dev->mm->pinned_vm) > lock_limit) {
>> +	if (!capable(CAP_IPC_LOCK) &&
>> +	    (npages + atomic64_read(&dev->mm->pinned_vm) > lock_limit)) {
>>   		ret = -ENOMEM;
>>   		goto unlock;
>>   	}
>> -- 
>> 2.18.1


      reply	other threads:[~2021-03-03  4:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-02  9:14 [PATCH] vhost-vdpa: honor CAP_IPC_LOCK Jason Wang
2021-03-02  9:51 ` Michael S. Tsirkin
2021-03-02 10:52   ` Jason Wang [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=4f3dcc1e-b95d-f17c-b371-52119d693d10@redhat.com \
    --to=jasowang@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).