From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Probable memory leak issue
Date: Sun, 21 Sep 2008 15:08:42 +0000 [thread overview]
Message-ID: <20080921170842.1e5e180c@hyperion.delvare> (raw)
On Thu, 31 Jul 2008 12:48:49 +0200, Souley Madougou wrote:
> Dear developers,
>
> I suspect that there is a memory leak issue in your code. In
> sensors_parse_chip_name() you are allocating memory in the following line:
> res->prefix = strndup(name, dash - name);
>
> In some circonstances, this memory is not freed in the sensors_cleanup()
> function.
Can you please send a patch fixing this problem you're seeing? If not,
please at least tell which version of lm-sensors you're looking at, and
what circumstances it takes to trigger the leak, so that I get a chance
to reproduce and fix it.
Thanks,
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next reply other threads:[~2008-09-21 15:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-21 15:08 Jean Delvare [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-07-31 10:48 [lm-sensors] Probable memory leak issue Souley Madougou
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=20080921170842.1e5e180c@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=lm-sensors@vger.kernel.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.