mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Hao Ge <hao.ge@linux.dev>
Cc: jack@suse.cz, sandeen@redhat.com, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, Hao Ge <gehao@kylinos.cn>
Subject: Re: [PATCH] isofs: avoid memory leak in iocharset
Date: Wed, 6 Nov 2024 13:40:00 +0100	[thread overview]
Message-ID: <20241106124000.kcrscsv5nrtporjs@quack3> (raw)
In-Reply-To: <20241106082841.51773-1-hao.ge@linux.dev>

On Wed 06-11-24 16:28:41, Hao Ge wrote:
> From: Hao Ge <gehao@kylinos.cn>
> 
> A memleak was found as below:
> 
> unreferenced object 0xffff0000d10164d8 (size 8):
>   comm "pool-udisksd", pid 108217, jiffies 4295408555
>   hex dump (first 8 bytes):
>     75 74 66 38 00 cc cc cc                          utf8....
>   backtrace (crc de430d31):
>     [<ffff800081046e6c>] kmemleak_alloc+0xb8/0xc8
>     [<ffff8000803e6c3c>] __kmalloc_node_track_caller_noprof+0x380/0x474
>     [<ffff800080363b74>] kstrdup+0x70/0xfc
>     [<ffff80007bb3c6a4>] isofs_parse_param+0x228/0x2c0 [isofs]
>     [<ffff8000804d7f68>] vfs_parse_fs_param+0xf4/0x164
>     [<ffff8000804d8064>] vfs_parse_fs_string+0x8c/0xd4
>     [<ffff8000804d815c>] vfs_parse_monolithic_sep+0xb0/0xfc
>     [<ffff8000804d81d8>] generic_parse_monolithic+0x30/0x3c
>     [<ffff8000804d8bfc>] parse_monolithic_mount_data+0x40/0x4c
>     [<ffff8000804b6a64>] path_mount+0x6c4/0x9ec
>     [<ffff8000804b6e38>] do_mount+0xac/0xc4
>     [<ffff8000804b7494>] __arm64_sys_mount+0x16c/0x2b0
>     [<ffff80008002b8dc>] invoke_syscall+0x7c/0x104
>     [<ffff80008002ba44>] el0_svc_common.constprop.1+0xe0/0x104
>     [<ffff80008002ba94>] do_el0_svc+0x2c/0x38
>     [<ffff800081041108>] el0_svc+0x3c/0x1b8
> 
> The opt->iocharset is freed inside the isofs_fill_super function,
> But there may be situations where it's not possible to
> enter this function.
> 
> For example, in the get_tree_bdev_flags function,when
> encountering the situation where "Can't mount, would change RO state,"
> In such a case, isofs_fill_super will not have the opportunity
> to be called,which means that opt->iocharset will not have the chance
> to be freed,ultimately leading to a memory leak.
> 
> Let's move the memory freeing of opt->iocharset into
> isofs_free_fc function.
> 
> Fixes: 1b17a46c9243 ("isofs: convert isofs to use the new mount API")
> Signed-off-by: Hao Ge <gehao@kylinos.cn>

Thanks. I've added the patch to my tree.

								Honza
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR

  reply	other threads:[~2024-11-06 12:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-06  8:28 Hao Ge
2024-11-06 12:40 ` Jan Kara [this message]
2024-11-06 18:59 ` Eric Sandeen

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=20241106124000.kcrscsv5nrtporjs@quack3 \
    --to=jack@suse.cz \
    --cc=gehao@kylinos.cn \
    --cc=hao.ge@linux.dev \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sandeen@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

all inboxes | Powered by JetHome®