From: Sascha Hauer <s.hauer@pengutronix.de>
To: quanyang.wang@windriver.com
Cc: richard@nod.at, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ubifs: fix memory leak from c->sup_node
Date: Tue, 14 Jan 2020 10:20:51 +0100 [thread overview]
Message-ID: <20200114092051.autszasi2rmywtyk@pengutronix.de> (raw)
In-Reply-To: <20200114054311.8984-1-quanyang.wang@windriver.com>
On Tue, Jan 14, 2020 at 01:43:11PM +0800, quanyang.wang@windriver.com wrote:
> From: Quanyang Wang <quanyang.wang@windriver.com>
>
> The c->sup_node is allocated in function ubifs_read_sb_node but
> is not freed. This will cause memory leak as below:
>
> unreferenced object 0xbc9ce000 (size 4096):
> comm "mount", pid 500, jiffies 4294952946 (age 315.820s)
> hex dump (first 32 bytes):
> 31 18 10 06 06 7b f1 11 02 00 00 00 00 00 00 00 1....{..........
> 00 10 00 00 06 00 00 00 00 00 00 00 08 00 00 00 ................
> backtrace:
> [<d1c503cd>] ubifs_read_superblock+0x48/0xebc
> [<a20e14bd>] ubifs_mount+0x974/0x1420
> [<8589ecc3>] legacy_get_tree+0x2c/0x50
> [<5f1fb889>] vfs_get_tree+0x28/0xfc
> [<bbfc7939>] do_mount+0x4f8/0x748
> [<4151f538>] ksys_mount+0x78/0xa0
> [<d59910a9>] ret_fast_syscall+0x0/0x54
> [<1cc40005>] 0x7ea02790
>
> Free it in ubifs_umount and in the error path of mount_ubifs.
>
> Fixes: fd6150051bec ("ubifs: Store read superblock node")
> Signed-off-by: Quanyang Wang <quanyang.wang@windriver.com>
Looks good.
Reviewed-by: Sascha Hauer <s.hauer@pengutronix.de>
Sascha
> ---
> fs/ubifs/super.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/fs/ubifs/super.c b/fs/ubifs/super.c
> index 7d4547e5202d..a4412c259bb3 100644
> --- a/fs/ubifs/super.c
> +++ b/fs/ubifs/super.c
> @@ -1599,6 +1599,7 @@ static int mount_ubifs(struct ubifs_info *c)
> vfree(c->ileb_buf);
> vfree(c->sbuf);
> kfree(c->bottom_up_buf);
> + kfree(c->sup_node);
> ubifs_debugging_exit(c);
> return err;
> }
> @@ -1641,6 +1642,7 @@ static void ubifs_umount(struct ubifs_info *c)
> vfree(c->ileb_buf);
> vfree(c->sbuf);
> kfree(c->bottom_up_buf);
> + kfree(c->sup_node);
> ubifs_debugging_exit(c);
> }
>
> --
> 2.17.1
>
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2020-01-14 9:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 5:43 quanyang.wang
2020-01-14 9:20 ` Sascha Hauer [this message]
2020-01-16 23:54 ` Richard Weinberger
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=20200114092051.autszasi2rmywtyk@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=quanyang.wang@windriver.com \
--cc=richard@nod.at \
/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
all inboxes | Powered by JetHome®