From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Juergen Gross <jgross@suse.com>
Cc: minios-devel@lists.xenproject.org,
xen-devel@lists.xenproject.org, wl@xen.org
Subject: Re: [PATCH 1/3] mini-os: fix double free() in netfront
Date: Thu, 9 Apr 2020 16:33:02 +0200 [thread overview]
Message-ID: <20200409143302.4kcbb3rf7rfxqkhq@function> (raw)
In-Reply-To: <20200409141240.28876-2-jgross@suse.com>
Juergen Gross, le jeu. 09 avril 2020 16:12:38 +0200, a ecrit:
> Commit d225f4012d69a19 ("Save/Restore Support: Add suspend/restore
> support for netfront") introduced a regression in form of freeing a
> netfront device structure twice.
>
> Fix that.
>
> Coverity-ID: 1433637
> Fixes: d225f4012d69a19 ("Save/Restore Support: Add suspend/restore support for netfront")
> Signed-off-by: Juergen Gross <jgross@suse.com>
Reviewed-by: Samuel Thibault <samuel.thibault@ens-lyon.org>
> ---
> netfront.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/netfront.c b/netfront.c
> index 50b3a57..fe7bb62 100644
> --- a/netfront.c
> +++ b/netfront.c
> @@ -584,8 +584,6 @@ void shutdown_netfront(struct netfront_dev *dev)
> list->refcount--;
> if (list->refcount == 0) {
> _shutdown_netfront(dev);
> - free(dev->nodename);
> - free(dev);
>
> to_del = list;
> if (to_del == dev_list) {
> --
> 2.16.4
>
next prev parent reply other threads:[~2020-04-09 14:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-09 14:12 [PATCH 0/3] mini-os: fix several double frees and memory leaks Juergen Gross
2020-04-09 14:12 ` [PATCH 1/3] mini-os: fix double free() in netfront Juergen Gross
2020-04-09 14:33 ` Samuel Thibault [this message]
2020-04-09 14:12 ` [PATCH 2/3] mini-os: fix double free() in xenbus Juergen Gross
2020-04-09 14:34 ` Samuel Thibault
2020-04-09 14:12 ` [PATCH 3/3] mini-os: fix several memory leaks related to xenbus Juergen Gross
2020-04-09 14:35 ` Samuel Thibault
2020-04-09 14:46 ` Wei Liu
2020-04-09 14:30 ` [PATCH 0/3] mini-os: fix several double frees and memory leaks Wei Liu
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=20200409143302.4kcbb3rf7rfxqkhq@function \
--to=samuel.thibault@ens-lyon.org \
--cc=jgross@suse.com \
--cc=minios-devel@lists.xenproject.org \
--cc=wl@xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.