From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932166AbcH0QNL (ORCPT ); Sat, 27 Aug 2016 12:13:11 -0400 Received: from mout.web.de ([217.72.192.78]:51898 "EHLO mout.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753872AbcH0QNJ (ORCPT ); Sat, 27 Aug 2016 12:13:09 -0400 Subject: Re: KVM-S390: Less function calls in kvm_s390_import_bp_data() after error detection To: =?UTF-8?Q?Christian_Borntr=c3=a4ger?= References: <82b84c9c-38a4-4d17-910f-312668dbae01@users.sourceforge.net> <47f88a11-b949-28ed-5589-925888a37574@users.sourceforge.net> Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org, Cornelia Huck , David Hildenbrand , Heiko Carstens , Martin Schwidefsky , Paolo Bonzini , =?UTF-8?B?UmFkaW0gS3LEjW3DocWZ?= , LKML , kernel-janitors@vger.kernel.org, Julia Lawall From: SF Markus Elfring Message-ID: <05fa56cb-843e-39bd-847d-1b31b5a726b5@users.sourceforge.net> Date: Sat, 27 Aug 2016 18:12:33 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:cgTRKjL6iB48tW4IyLEIWskkLzYY3Jpo78TfslQjYbCZ7hHOGKt fRh6AJOaLFyBIE+GKyIe9qJSqyyK1P3VyEDc6BU+2wmxlZDAb7zSAk1p49WLr34darpbmQd E2jdVnj/VxXpAnOOtSwb+2rXqQDzPOzFyZQjpZ2aLfoXgp9g40POBGBXv9UaVkHCaZzPbsF Yfr10WJJudl1wUg2uXx8g== X-UI-Out-Filterresults: notjunk:1;V01:K0:yeLj0Zn1YAA=:INeTrwI9DWasQnAUlRcUON 9TAmIkIOkDaAFZwCAwqh4ms68zI7nebAn7Irf6FDe5xW4TBlCCn68wBINZk4K/PhqimV7RE3Q /Q63ud7YoBehHP4oLGFc/3QPw1kP73IIRAgbL+QlOmfwJw7SWDpy9xzgpiIlkd1MtYQHY4nj0 WJ1SHz+tbe6HhwWuIzmiez/ToNBQ1cRsX0Lo9uLCrIM2AinZ2XlP8j3cFVN1P5SHJKYG9Qxpj J9+MyKY86JpOScA4moMmCRvPEbWWz8TLMD3toPK9Gl8gjK0buZc8opfycP9upCqCo7jSWRPrR F5N2H8DtJ4VIB1SnFL76AQM0mW8WbKBxpcyLd56WIAdcGvPWbsDXyor5oy7Vk7voP7Yue4HiV w45UceTiBich03vaq4lTRZjFhaRR1Ov+rfsQGQNntC6+aWYG1AqbjrWtKkHDTfRAepQZjGeH0 VaxoDaZrMx6Tz+mCdjoFJlW7OWlggaJ4FEsx29ogC553f0PYGGvucznsgc1wnJQBtso81E7oi OY5bUZQbboWkizTidktMOnzACre87vGQz3LtyZByz6p42RFGJfgtdWYZOUHQGpK072zJd63Eg SOAdfyVk3Cc9fXmQArhPGPNmdDyv5IRLE/Ph18hrZTVw1qfxUkUTcBlDlxcfYXHNuXwIfnQqb P2HlJQZ9V4ovqvQCp1HROcT1f4+iiuj9+HDWi/fcCUmmz79NKKqKXdfjp+KGSf0lLknbPMblu /mUEV3R+XkeJwj84rDo9tZBSV6w0TorYXVtbgnc+iPIdCNoWGWmUIqsMPJWlHOFmkM3OuCHG3 clCMNWo Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org >> @@ -273,10 +273,12 @@ int kvm_s390_import_bp_data(struct kvm_vcpu *vcpu, >> vcpu->arch.guestdbg.nr_hw_wp = nr_wp; >> vcpu->arch.guestdbg.hw_wp_info = wp_info; >> return 0; >> -error: >> - kfree(bp_data); >> - kfree(wp_info); >> +free_bp_info: >> kfree(bp_info); >> +free_wp_info: >> + kfree(wp_info); >> +free_bp_data: >> + kfree(bp_data); >> return ret; >> } > > I agree with Cornelia, This is generally fine. > while it seems correct from a technical point of view, Thanks for another bit of acknowledgement. > it will make the code harder to maintain. I agree that there some efforts and challenges involved. > For example if we ever add a new malloc and remove another one Do you see any changes coming from this direction? > over time we would need to reshuffle the labels This can occasionally happen, can't it? > and this did went wrong several times in the past. Would you like to add any corresponding software development experiences to discussions around a topic like "CodingStyle: add some more error handling guidelines"? https://www.spinics.net/lists/linux-doc/msg39307.html http://marc.info/?l=linux-doc&m=147187538413914 Regards, Markus