From: Gioh Kim <gi-oh.kim@profitbricks.com>
To: dm-devel@redhat.com
Subject: memory leak from orphan_path()
Date: Thu, 14 Jul 2016 16:52:45 +0200 [thread overview]
Message-ID: <5787A73D.8050403@profitbricks.com> (raw)
Hello,
I've found that orphan_path() function just set pp->getuid as NULL.
But it can have a string allocated by strdup.
I think it should be freed by free().
I sent a patch and experiment result but I got a reply that my email is
'unprocessed'.
So I could not attach my patch but it's very easy for you to catch.
I'd appreciate if you would give me any feedback.
--
Best regards,
Gioh Kim
reply other threads:[~2016-07-14 14:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5787A73D.8050403@profitbricks.com \
--to=gi-oh.kim@profitbricks.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