From: David Miller <davem@davemloft.net>
To: navid.emamdoost@gmail.com
Cc: emamd001@umn.edu, smccaman@umn.edu, kjlu@umn.edu,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] net: qrtr: fix memort leak in qrtr_tun_write_iter
Date: Thu, 12 Sep 2019 12:59:13 +0200 (CEST) [thread overview]
Message-ID: <20190912.125913.284555259841442636.davem@davemloft.net> (raw)
In-Reply-To: <20190911150907.18251-1-navid.emamdoost@gmail.com>
From: Navid Emamdoost <navid.emamdoost@gmail.com>
Date: Wed, 11 Sep 2019 10:09:02 -0500
> In qrtr_tun_write_iter the allocated kbuf should be release in case of
> error or success return.
>
> v2 Update: Thanks to David Miller for pointing out the release on success
> path as well.
>
> Signed-off-by: Navid Emamdoost <navid.emamdoost@gmail.com>
Applied, thanks.
prev parent reply other threads:[~2019-09-12 10:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 0:37 [PATCH] net: qrtr: fix memort leak in qrtr_tun_write_iter Navid Emamdoost
2019-09-11 8:13 ` David Miller
2019-09-11 15:09 ` [PATCH v2] " Navid Emamdoost
2019-09-12 10:59 ` David Miller [this message]
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=20190912.125913.284555259841442636.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=emamd001@umn.edu \
--cc=kjlu@umn.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=navid.emamdoost@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=smccaman@umn.edu \
/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).