From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Juergen Gross <jgross@suse.com>
Cc: Quentin Lambert <lambert.quentin@gmail.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
David Vrabel <david.vrabel@citrix.com>,
"James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
xen-devel@lists.xenproject.org, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] xen-scsifront: Add a missing call to kfree
Date: Tue, 22 Nov 2016 03:40:00 +0000 [thread overview]
Message-ID: <yq1twb0yygf.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <1320a162-dc36-5833-a746-367134dae5e7@suse.com> (Juergen Gross's message of "Mon, 21 Nov 2016 07:01:36 +0100")
>>>>> "Juergen" = Juergen Gross <jgross@suse.com> writes:
Juergen,
Juergen> On 19/11/16 19:22, Quentin Lambert wrote:
>> Most error branches following the call to kmalloc contain a call to
>> kfree. This patch add these calls where they are missing.
>>
>> This issue was found with Hector.
>>
>> Signed-off-by: Quentin Lambert <lambert.quentin@gmail.com>
Juergen> Nice catch. I think this will need some more work, I'll do a
Juergen> follow-on patch.
Juergen> Reviewed-by: Juergen Gross <jgross@suse.com>
Are you taking this patch through the Xen tree or should I queue it up?
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2016-11-22 3:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-19 18:22 [PATCH] xen-scsifront: Add a missing call to kfree Quentin Lambert
2016-11-21 6:01 ` Juergen Gross
2016-11-22 3:40 ` Martin K. Petersen [this message]
2016-11-22 5:19 ` Juergen Gross
2016-11-25 21:28 ` Dan Carpenter
2016-12-05 20:53 ` Dan Carpenter
2016-12-06 5:45 ` Juergen Gross
2016-12-06 10:22 ` Dan Carpenter
2016-11-24 8:24 ` Juergen Gross
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=yq1twb0yygf.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=jgross@suse.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=lambert.quentin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--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