From: Germano Percossi <germano.percossi@citrix.com>
To: dm-devel@redhat.com
Subject: Re: [PATCH 1/1] multipath: fix memory leak and segfault in reconfigure
Date: Tue, 23 Feb 2016 15:17:09 +0000 [thread overview]
Message-ID: <56CC77F5.2020004@citrix.com> (raw)
In-Reply-To: <1455219054-13122-1-git-send-email-germano.percossi@citrix.com>
Ping
On 02/11/2016 07:30 PM, Germano Percossi wrote:
> Within the reconfigure function, the global pointer conf is
> stored in a local variable and then assigned NULL.
> If load_config should fail, for any reason, we end up with
> a memory leak, as soon as we leave the function, and with
> the global pointer conf set to NULL, leading to a segfault
> as soon as it is dereferenced.
>
> I tested it by calling a reconfigure and making the first
> allocation in load_config fail but any failure in load_config
> would do.
>>From a user perspective the CLI reports "fail".
>
> If something like this should happen there are at least 2 possible
> scenarios:
>
> 1) If a second immediate reconfigure succeeds, the conf now is fine but
> the leak stays
> 2) If the previous point does not happen, any command trying to access
> "conf" would fail. On my test box a "show conf" segfaulted.
>
> The fix is simple but in case of failure at least the previous
> conf is kept in memory without leaks or segfaluts
>
> Signed-off-by: Germano Percossi <germano.percossi@citrix.com>
> ---
> multipathd/main.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/multipathd/main.c b/multipathd/main.c
> index 04f6d02..f83c849 100644
> --- a/multipathd/main.c
> +++ b/multipathd/main.c
> @@ -1551,6 +1551,8 @@ reconfigure (struct vectors * vecs)
> configure(vecs, 1);
> free_config(old);
> retval = 0;
> + } else {
> + conf = old;
> }
>
> running_state = DAEMON_RUNNING;
>
next prev parent reply other threads:[~2016-02-23 15:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 19:30 [PATCH 1/1] multipath: fix memory leak and segfault in reconfigure Germano Percossi
2016-02-23 15:17 ` Germano Percossi [this message]
2016-04-18 10:42 ` Germano Percossi
2016-04-18 11:12 ` Christophe Varoqui
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=56CC77F5.2020004@citrix.com \
--to=germano.percossi@citrix.com \
--cc=dm-devel@redhat.com \
/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).