From: scott_gzh@163.com
To: phillip@squashfs.org.uk
Cc: linux-kernel@vger.kernel.org, Scott GUO <scottzhguo@tencent.com>
Subject: [PATCH v2] squashfs: Avoid mem leak in squashfs_fill_super()
Date: Tue, 12 Aug 2025 11:04:03 +0800 [thread overview]
Message-ID: <20250812030403.517269-1-scott_gzh@163.com> (raw)
From: Scott GUO <scottzhguo@tencent.com>
If sb_min_blocksize() returns 0, -EINVAL was returned without freeing
sb->s_fs_info, causing mem leak.
Fix it by calling and checking result of sb_min_blocksize() before
kzalloc.
Fixes: 734aa85390ea ("Squashfs: check return result of sb_min_blocksize")
Signed-off-by: Scott GUO <scottzhguo@tencent.com>
---
v2:
Adjust commit message based on Markus' advice, and refine fix
following Phillip's comment.
---
fs/squashfs/super.c | 14 ++++++++------
1 file changed, 8 insertions(+), 6 deletions(-)
diff --git a/fs/squashfs/super.c b/fs/squashfs/super.c
index 992ea0e37257..073462b098c5 100644
--- a/fs/squashfs/super.c
+++ b/fs/squashfs/super.c
@@ -188,9 +188,16 @@ static int squashfs_fill_super(struct super_block *sb, struct fs_context *fc)
unsigned int fragments;
u64 lookup_table_start, xattr_id_table_start, next_table;
int err;
+ int devblksize;
TRACE("Entered squashfs_fill_superblock\n");
+ devblksize = sb_min_blocksize(sb, SQUASHFS_DEVBLK_SIZE);
+ if (!devblksize) {
+ errorf(fc, "squashfs: unable to set blocksize\n");
+ return -EINVAL;
+ }
+
sb->s_fs_info = kzalloc(sizeof(*msblk), GFP_KERNEL);
if (sb->s_fs_info == NULL) {
ERROR("Failed to allocate squashfs_sb_info\n");
@@ -201,12 +208,7 @@ static int squashfs_fill_super(struct super_block *sb, struct fs_context *fc)
msblk->panic_on_errors = (opts->errors == Opt_errors_panic);
- msblk->devblksize = sb_min_blocksize(sb, SQUASHFS_DEVBLK_SIZE);
- if (!msblk->devblksize) {
- errorf(fc, "squashfs: unable to set blocksize\n");
- return -EINVAL;
- }
-
+ msblk->devblksize = devblksize;
msblk->devblksize_log2 = ffz(~msblk->devblksize);
mutex_init(&msblk->meta_index_mutex);
--
2.41.3
next reply other threads:[~2025-08-12 3:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 3:04 scott_gzh [this message]
2025-08-12 15:57 ` Markus Elfring
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=20250812030403.517269-1-scott_gzh@163.com \
--to=scott_gzh@163.com \
--cc=linux-kernel@vger.kernel.org \
--cc=phillip@squashfs.org.uk \
--cc=scottzhguo@tencent.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®