From: Lukas Straub <lukasstraub2@web.de>
To: Derek Su <dereksu@qnap.com>
Cc: lizhijian@cn.fujitsu.com, chyang@qnap.com, jasowang@redhat.com,
qemu-devel@nongnu.org, ctcheng@qnap.com, chen.zhang@intel.com,
jwsu1986@gmail.com
Subject: Re: [PATCH v4 1/2] net/colo-compare.c: Fix memory leak in packet_enqueue()
Date: Mon, 6 Apr 2020 00:12:05 +0200 [thread overview]
Message-ID: <20200406001205.14e986d3@luklap> (raw)
In-Reply-To: <20200328124646.7778-2-dereksu@qnap.com>
[-- Attachment #1: Type: text/plain, Size: 2310 bytes --]
On Sat, 28 Mar 2020 20:46:45 +0800
Derek Su <dereksu@qnap.com> wrote:
> The patch is to fix the "pkt" memory leak in packet_enqueue().
> The allocated "pkt" needs to be freed if the colo compare
> primary or secondary queue is too big.
>
> Signed-off-by: Derek Su <dereksu@qnap.com>
Looks good and works well in my tests.
Reviewed-by: Lukas Straub <lukasstraub2@web.de>
Tested-by: Lukas Straub <lukasstraub2@web.de>
Regards,
Lukas Straub
> ---
> net/colo-compare.c | 23 +++++++++++++++--------
> 1 file changed, 15 insertions(+), 8 deletions(-)
>
> diff --git a/net/colo-compare.c b/net/colo-compare.c
> index 7ee17f2cf8..cdd87b2aa8 100644
> --- a/net/colo-compare.c
> +++ b/net/colo-compare.c
> @@ -120,6 +120,10 @@ enum {
> SECONDARY_IN,
> };
>
> +static const char *colo_mode[] = {
> + [PRIMARY_IN] = "primary",
> + [SECONDARY_IN] = "secondary",
> +};
>
> static int compare_chr_send(CompareState *s,
> const uint8_t *buf,
> @@ -215,6 +219,7 @@ static int packet_enqueue(CompareState *s, int mode, Connection **con)
> ConnectionKey key;
> Packet *pkt = NULL;
> Connection *conn;
> + int ret;
>
> if (mode == PRIMARY_IN) {
> pkt = packet_new(s->pri_rs.buf,
> @@ -243,16 +248,18 @@ static int packet_enqueue(CompareState *s, int mode, Connection **con)
> }
>
> if (mode == PRIMARY_IN) {
> - if (!colo_insert_packet(&conn->primary_list, pkt, &conn->pack)) {
> - error_report("colo compare primary queue size too big,"
> - "drop packet");
> - }
> + ret = colo_insert_packet(&conn->primary_list, pkt, &conn->pack);
> } else {
> - if (!colo_insert_packet(&conn->secondary_list, pkt, &conn->sack)) {
> - error_report("colo compare secondary queue size too big,"
> - "drop packet");
> - }
> + ret = colo_insert_packet(&conn->secondary_list, pkt, &conn->sack);
> }
> +
> + if (!ret) {
> + error_report("colo compare %s queue size too big,"
> + "drop packet", colo_mode[mode]);
> + packet_destroy(pkt, NULL);
> + pkt = NULL;
> + }
> +
> *con = conn;
>
> return 0;
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-04-05 22:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-28 12:46 [PATCH v4 0/2] COLO: handling of the full primary or secondary queue Derek Su
2020-03-28 12:46 ` [PATCH v4 1/2] net/colo-compare.c: Fix memory leak in packet_enqueue() Derek Su
2020-03-31 1:14 ` Zhang, Chen
2020-04-05 22:12 ` Lukas Straub [this message]
2020-03-28 12:46 ` [PATCH v4 2/2] net/colo-compare.c: handling of the full primary or secondary queue Derek Su
2020-03-31 1:15 ` Zhang, Chen
2020-04-05 22:11 ` Lukas Straub
2020-04-08 19:18 ` Lukas Straub
2020-04-09 6:59 ` Zhang, Chen
2020-04-09 7:10 ` Derek Su
2020-04-09 9:02 ` Zhang, Chen
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=20200406001205.14e986d3@luklap \
--to=lukasstraub2@web.de \
--cc=chen.zhang@intel.com \
--cc=chyang@qnap.com \
--cc=ctcheng@qnap.com \
--cc=dereksu@qnap.com \
--cc=jasowang@redhat.com \
--cc=jwsu1986@gmail.com \
--cc=lizhijian@cn.fujitsu.com \
--cc=qemu-devel@nongnu.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).