From: George Dunlap <george.dunlap@citrix.com>
To: Lasya Venneti <comethalley61@gmail.com>,
Dario Faggioli <dario.faggioli@citrix.com>
Cc: xen-devel@lists.xenproject.org, Wei Liu <wei.liu2@citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
Lars Kurth <lars.kurth@citrix.com>
Subject: Re: [PATCH] 'dom' error handled, by raising ENOMEM if failure occurs. 'xs_fd' leak handled in success path.
Date: Tue, 27 Oct 2015 11:07:21 +0000 [thread overview]
Message-ID: <562F5AE9.10009@citrix.com> (raw)
In-Reply-To: <CAAbK429W-ChNF3cr5cKMsiYgD2A_=MGgvJ4mCGpp146AJvq=XA@mail.gmail.com>
On 27/10/15 11:04, Lasya Venneti wrote:
> On 27 October 2015 at 16:25, Dario Faggioli <dario.faggioli@citrix.com>
> wrote:
>
>> On Wed, 2015-10-28 at 03:49 +0530, Lasya wrote:
>>
>> The description of the patch, that you previously put in a separate
>> email, should live here.
>>
> Oh, I had thought no cover letter was needed. Hence, I didn't put in a
> description, I shall add it in v3. :)
Please also read carefully the section titled "Making good patches" in
the Submitting Xen Project Patches wiki page [1].
[1] http://wiki.xenproject.org/wiki/Submitting_Xen_Project_Patches
-George
>
>>
>> Also, this is the second version of a patch. That should be evident
>> from the subject line (something like "[PATCH v2]").
>>
>> And still about the subject line, it's a bit long. It must contain a
>> very quick hint at what the patch is about, then all the details go in
>> the patch description (also called changelog), i.e., right in here. :-)
>>
> The subject line was picked up from the commit message, I shall put a
> concise one this time.
>
>>
>>> Signed-off-by: Lasya Venneti <comethalley61@gmail.com>
>>> ---
>>> tools/xenstore/init-xenstore-domain.c | 7 ++++++-
>>> 1 file changed, 6 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/tools/xenstore/init-xenstore-domain.c
>>> b/tools/xenstore/init-xenstore-domain.c
>>> index 0d12169..b413b09 100644
>>> --- a/tools/xenstore/init-xenstore-domain.c
>>> +++ b/tools/xenstore/init-xenstore-domain.c
>>> @@ -42,6 +42,10 @@ static int build(xc_interface *xch, int argc,
>>> char** argv)
>>> snprintf(cmdline, 512, "--event %d --internal-db", rv);
>>>
>>> dom = xc_dom_allocate(xch, cmdline, NULL);
>>> + if(dom==NULL) {
>>> + rv=ENOMEM;
>>> + goto err;
>>> + }
>>>
>> A lot of spaces are missing...
>>
>>> rv = xc_dom_kernel_file(dom, argv[1]);
>> ^ ^
>> | |
>> -----------------------------------------------
>> |
>> Just, for instance, compare what you added with this: ---
>>
>>> if (rv) goto err;
>> ^
>> |
>> --------
>> |
>> And with this: ---
>>
>>> @@ -70,7 +74,8 @@ static int build(xc_interface *xch, int argc,
>>> char** argv)
>>> if (rv) goto err;
>>> rv = xc_domain_unpause(xch, domid);
>>> if (rv) goto err;
>>> -
>>> +
>>>
>>
> Dario, I wasn't look at the individual spaces, just the line breaks. Will
> be careful this time.
>
>> What happened here?
>>
>>> + close(xs_fd);
>>> return 0;
>>>
>> Also, Wei suggested to send two patches, one for fixing the error
>> handling for xc_dom_allocate(), and another one for stopping leaking
>> the fd on the success path.
>>
>> Regards,
>> Dario
>>
> Okay. I shall send them in as two patches.
>
> Thank you for being so patient with this.
> Regards
> Lasya V
>
>> --
>> <<This happens because I choose it to happen!>> (Raistlin Majere)
>> -----------------------------------------------------------------
>> Dario Faggioli, Ph.D, http://about.me/dario.faggioli
>> Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
>>
>>
>
next prev parent reply other threads:[~2015-10-27 11:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 22:19 [PATCH] 'dom' error handled, by raising ENOMEM if failure occurs. 'xs_fd' leak handled in success path Lasya
2015-10-27 10:55 ` Dario Faggioli
2015-10-27 11:04 ` Lasya Venneti
2015-10-27 11:07 ` George Dunlap [this message]
2015-10-27 11:25 ` Lasya Venneti
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=562F5AE9.10009@citrix.com \
--to=george.dunlap@citrix.com \
--cc=comethalley61@gmail.com \
--cc=dario.faggioli@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=lars.kurth@citrix.com \
--cc=wei.liu2@citrix.com \
--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;
as well as URLs for NNTP newsgroup(s).