From: David Gibson <david@gibson.dropbear.id.au>
To: Serhii Popovych <spopovyc@redhat.com>
Cc: linux-kernel@vger.kernel.org, michael@ellerman.id.au,
paulus@samba.org, linuxppc-dev@lists.ozlabs.org,
kvm-ppc@vger.kernel.org
Subject: Re: [PATCH 1/4] KVM: PPC: Book3S HV: Drop prepare_done from struct kvm_resize_hpt and cleanups
Date: Thu, 30 Nov 2017 14:40:40 +1100 [thread overview]
Message-ID: <20171130034040.GO3023@umbus.fritz.box> (raw)
In-Reply-To: <1511973506-65683-2-git-send-email-spopovyc@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 3855 bytes --]
On Wed, Nov 29, 2017 at 11:38:23AM -0500, Serhii Popovych wrote:
> Replace ->prepare_done flag functionality with special handling
> of -EBUSY in ->error as indicator that allocation work is running.
>
> Besides cosmetics this reduces size of struct kvm_resize_hpt by
> __alignof__(struct kvm_hpt_info) and saves few bytes of code.
>
> While there correct comment in struct kvm_resize_hpt about locking
> used to protect access to certain fields.
>
> Assert with BUG_ON() in case of HPT allocation thread work runs
> more than once for resize request or resize_hpt_allocate()
> returns -EBUSY that is treated specially.
>
> Change comparison against zero to make checkpatch.pl happy.
>
> Signed-off-by: Serhii Popovych <spopovyc@redhat.com>
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
> ---
> arch/powerpc/kvm/book3s_64_mmu_hv.c | 42 ++++++++++++++++++++++---------------
> 1 file changed, 25 insertions(+), 17 deletions(-)
>
> diff --git a/arch/powerpc/kvm/book3s_64_mmu_hv.c b/arch/powerpc/kvm/book3s_64_mmu_hv.c
> index 235319c..0534aab 100644
> --- a/arch/powerpc/kvm/book3s_64_mmu_hv.c
> +++ b/arch/powerpc/kvm/book3s_64_mmu_hv.c
> @@ -65,11 +65,17 @@ struct kvm_resize_hpt {
> u32 order;
>
> /* These fields protected by kvm->lock */
> +
> + /* Possible values and their usage:
> + * <0 an error occurred during allocation,
> + * -EBUSY allocation is in the progress,
> + * 0 allocation made successfuly.
> + */
> int error;
> - bool prepare_done;
>
> - /* Private to the work thread, until prepare_done is true,
> - * then protected by kvm->resize_hpt_sem */
> + /* Private to the work thread, until error != -EBUSY,
> + * then protected by kvm->lock.
> + */
> struct kvm_hpt_info hpt;
> };
>
> @@ -1432,15 +1438,21 @@ static void resize_hpt_prepare_work(struct work_struct *work)
> struct kvm *kvm = resize->kvm;
> int err;
>
> + BUG_ON(resize->error != -EBUSY);
> +
> resize_hpt_debug(resize, "resize_hpt_prepare_work(): order = %d\n",
> resize->order);
>
> err = resize_hpt_allocate(resize);
>
> + /* We have strict assumption about -EBUSY
> + * when preparing for HPT resize.
> + */
> + BUG_ON(err == -EBUSY);
> +
> mutex_lock(&kvm->lock);
>
> resize->error = err;
> - resize->prepare_done = true;
>
> mutex_unlock(&kvm->lock);
> }
> @@ -1465,14 +1477,12 @@ long kvm_vm_ioctl_resize_hpt_prepare(struct kvm *kvm,
>
> if (resize) {
> if (resize->order == shift) {
> - /* Suitable resize in progress */
> - if (resize->prepare_done) {
> - ret = resize->error;
> - if (ret != 0)
> - resize_hpt_release(kvm, resize);
> - } else {
> + /* Suitable resize in progress? */
> + ret = resize->error;
> + if (ret == -EBUSY)
> ret = 100; /* estimated time in ms */
> - }
> + else if (ret)
> + resize_hpt_release(kvm, resize);
>
> goto out;
> }
> @@ -1492,6 +1502,8 @@ long kvm_vm_ioctl_resize_hpt_prepare(struct kvm *kvm,
> ret = -ENOMEM;
> goto out;
> }
> +
> + resize->error = -EBUSY;
> resize->order = shift;
> resize->kvm = kvm;
> INIT_WORK(&resize->work, resize_hpt_prepare_work);
> @@ -1546,16 +1558,12 @@ long kvm_vm_ioctl_resize_hpt_commit(struct kvm *kvm,
> if (!resize || (resize->order != shift))
> goto out;
>
> - ret = -EBUSY;
> - if (!resize->prepare_done)
> - goto out;
> -
> ret = resize->error;
> - if (ret != 0)
> + if (ret)
> goto out;
>
> ret = resize_hpt_rehash(resize);
> - if (ret != 0)
> + if (ret)
> goto out;
>
> resize_hpt_pivot(resize);
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-11-30 4:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 16:38 [PATCH 0/4] Fix use after free in HPT resizing code and related minor improvements Serhii Popovych
2017-11-29 16:38 ` [PATCH 1/4] KVM: PPC: Book3S HV: Drop prepare_done from struct kvm_resize_hpt and cleanups Serhii Popovych
2017-11-30 3:40 ` David Gibson [this message]
2017-11-29 16:38 ` [PATCH 2/4] KVM: PPC: Book3S HV: Improve kvmppc_allocate_hpt()/kvmppc_free_hpt() Serhii Popovych
2017-11-30 3:45 ` David Gibson
2017-11-29 16:38 ` [PATCH 3/4] KVM: PPC: Book3S HV: Fix use after free in case of multiple resize requests Serhii Popovych
2017-11-30 3:51 ` David Gibson
2017-11-29 16:38 ` [PATCH 4/4] KVM: PPC: Book3S HV: Remove redundant parameter from resize_hpt_release() Serhii Popovych
2017-11-30 3:53 ` David Gibson
2017-11-30 3:54 ` [PATCH 0/4] Fix use after free in HPT resizing code and related minor improvements David Gibson
2017-12-04 6:10 ` David Gibson
2017-12-04 12:22 ` Michael Ellerman
2017-12-04 14:43 ` Serhii Popovych
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=20171130034040.GO3023@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=kvm-ppc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=michael@ellerman.id.au \
--cc=paulus@samba.org \
--cc=spopovyc@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 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).