From: David Timber <dxdt@dev.snart.me>
To: Namjae Jeon <linkinjeon@kernel.org>,
Sungjong Seo <sj1557.seo@samsung.com>,
Yuezhang Mo <yuezhang.mo@sony.com>
Cc: linux-fsdevel@vger.kernel.org, David Timber <dxdt@dev.snart.me>
Subject: [PATCH v1 3/3] exfat: fix memory leak (upcase table)
Date: Tue, 5 May 2026 21:28:08 +0900 [thread overview]
Message-ID: <20260505122808.728020-3-dxdt@dev.snart.me> (raw)
In-Reply-To: <20260505122808.728020-1-dxdt@dev.snart.me>
Fix memory leak conditions due to exfat_free_upcase_table() not being
called.
Signed-off-by: David Timber <dxdt@dev.snart.me>
---
fs/exfat/super.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/fs/exfat/super.c b/fs/exfat/super.c
index e0a80d8f5f80..e9dc1e616fac 100644
--- a/fs/exfat/super.c
+++ b/fs/exfat/super.c
@@ -707,6 +707,7 @@ static int __exfat_fill_super(struct super_block *sb,
exfat_free_bitmap(sbi);
free_bh:
brelse(sbi->boot_bh);
+ exfat_free_upcase_table(sbi);
return ret;
}
@@ -802,6 +803,7 @@ static int exfat_get_tree(struct fs_context *fc)
static void exfat_free_sbi(struct exfat_sb_info *sbi)
{
+ exfat_free_upcase_table(sbi);
exfat_free_iocharset(sbi);
kfree(sbi);
}
--
2.53.0.1.ga224b40d3f.dirty
next prev parent reply other threads:[~2026-05-05 12:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 12:28 [PATCH v1 1/3] exfat: add volume limit bounds checks David Timber
2026-05-05 12:28 ` [PATCH v1 2/3] exfat: print warning upon block size calibration David Timber
2026-05-05 12:28 ` David Timber [this message]
2026-05-07 12:04 ` [PATCH v1 3/3] exfat: fix memory leak (upcase table) Yuezhang.Mo
2026-05-10 23:10 ` David Timber
2026-05-07 12:04 ` [PATCH v1 1/3] exfat: add volume limit bounds checks Yuezhang.Mo
2026-05-10 23:17 ` David Timber
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=20260505122808.728020-3-dxdt@dev.snart.me \
--to=dxdt@dev.snart.me \
--cc=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sj1557.seo@samsung.com \
--cc=yuezhang.mo@sony.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