From: Zhihao Cheng <chengzhihao1@huawei.com>
To: <richard@nod.at>, <ebiggers@google.com>, <terrelln@fb.com>
Cc: <linux-fscrypt@vger.kernel.org>, <linux-mtd@lists.infradead.org>
Subject: [PATCH v3 0/2] ubifs: Fix two kmemleaks in error path
Date: Mon, 8 Jan 2024 10:41:03 +0800 [thread overview]
Message-ID: <20240108024105.194516-1-chengzhihao1@huawei.com> (raw)
First memleak is found by mounting corrupted UBIFS image with chk_index
enabled.
Second memleak is found by powercut testing for encryption scenario.
v1->v2:
ubifs_symlink: Call fscrypt_free_inode() directly in error handling path.
Add 'Cc: stable@vger.kernel.org' and 'Suggested-by' tags in patch 2.
v2->v3:
Handle tnc releasing in error handling path in dbg_check_idx_size().
Zhihao Cheng (2):
ubifs: dbg_check_idx_size: Fix kmemleak if loading znode failed
ubifs: ubifs_symlink: Fix memleak of inode->i_link in error path
fs/ubifs/debug.c | 9 +++++++--
fs/ubifs/dir.c | 2 ++
fs/ubifs/tnc.c | 9 +--------
fs/ubifs/tnc_misc.c | 22 ++++++++++++++++++++++
fs/ubifs/ubifs.h | 1 +
5 files changed, 33 insertions(+), 10 deletions(-)
--
2.39.2
next reply other threads:[~2024-01-08 2:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 2:41 Zhihao Cheng [this message]
2024-01-08 2:41 ` [PATCH v3 1/2] ubifs: dbg_check_idx_size: Fix kmemleak if loading znode failed Zhihao Cheng
2024-01-08 2:41 ` [PATCH v3 2/2] ubifs: ubifs_symlink: Fix memleak of inode->i_link in error path Zhihao Cheng
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=20240108024105.194516-1-chengzhihao1@huawei.com \
--to=chengzhihao1@huawei.com \
--cc=ebiggers@google.com \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=terrelln@fb.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).