From: Ingo Molnar <mingo@kernel.org>
To: Nicholas Krause <xerofoify@gmail.com>
Cc: gleb@kernel.org, pbonzini@redhat.com, x86@kernel.org,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kvm:Return -ENOMEM directly for the function, kvm_create_lapic
Date: Thu, 21 May 2015 08:09:40 +0200 [thread overview]
Message-ID: <20150521060940.GB5615@gmail.com> (raw)
In-Reply-To: <1432169486-31846-1-git-send-email-xerofoify@gmail.com>
* Nicholas Krause <xerofoify@gmail.com> wrote:
> In order to make code paths easier to read in the function,
> kvm_create_lapic we return -ENOMEM when unable to allocate
> memory for a kvm_lapic structure pointer directly. This
> makes the code easier to read and cleaner then jumping
> to a goto label at the end of the function's body for
> returning just the error code, -ENOMEM.
>
> Signed-off-by: Nicholas Krause <xerofoify@gmail.com>
> ---
> arch/x86/kvm/lapic.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/arch/x86/kvm/lapic.c b/arch/x86/kvm/lapic.c
> index 629af0f..88d0cce 100644
> --- a/arch/x86/kvm/lapic.c
> +++ b/arch/x86/kvm/lapic.c
> @@ -1687,7 +1687,7 @@ int kvm_create_lapic(struct kvm_vcpu *vcpu)
>
> apic = kzalloc(sizeof(*apic), GFP_KERNEL);
> if (!apic)
> - goto nomem;
> + return -ENOMEM;
>
> vcpu->arch.apic = apic;
>
> @@ -1718,7 +1718,6 @@ int kvm_create_lapic(struct kvm_vcpu *vcpu)
> return 0;
> nomem_free_apic:
> kfree(apic);
> -nomem:
> return -ENOMEM;
> }
NAK!
You just half destroyed the nice error handling cascade of labels.
Thanks,
Ingo
next parent reply other threads:[~2015-05-21 6:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1432169486-31846-1-git-send-email-xerofoify@gmail.com>
2015-05-21 6:09 ` Ingo Molnar [this message]
2015-05-21 12:22 ` [PATCH] kvm:Return -ENOMEM directly for the function, kvm_create_lapic Paolo Bonzini
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=20150521060940.GB5615@gmail.com \
--to=mingo@kernel.org \
--cc=gleb@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=x86@kernel.org \
--cc=xerofoify@gmail.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.