From: Disha Goel <disgoel@linux.ibm.com>
To: ltp@lists.linux.it
Cc: Disha Goel <disgoel@linux.ibm.com>
Subject: [LTP] [PATCH 1/2] memcg/memcontrol02: fix fd leak in cleanup path
Date: Fri, 7 Aug 2026 18:35:21 +0530 [thread overview]
Message-ID: <20260807130523.49068-1-disgoel@linux.ibm.com> (raw)
fd is initialized to 0 (a valid file descriptor) so the cleanup()
guard 'if (fd > -1)' would never trigger. Initialize to -1 and
add SAFE_CLOSE to prevent the descriptor leaking when a SAFE_*
macro calls tst_brk() during the pagecache allocation test.
Signed-off-by: Disha Goel <disgoel@linux.ibm.com>
---
testcases/kernel/controllers/memcg/memcontrol02.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/testcases/kernel/controllers/memcg/memcontrol02.c b/testcases/kernel/controllers/memcg/memcontrol02.c
index 0b79403c9..75a1e6d51 100644
--- a/testcases/kernel/controllers/memcg/memcontrol02.c
+++ b/testcases/kernel/controllers/memcg/memcontrol02.c
@@ -29,7 +29,7 @@
static size_t page_size;
static struct tst_cg_group *cg_child;
-static int fd;
+static int fd = -1;
static int file_to_all_error = 10;
static void alloc_anon_50M_check(void)
@@ -128,6 +128,8 @@ static void cleanup(void)
{
if (cg_child)
cg_child = tst_cg_group_rm(cg_child);
+ if (fd > -1)
+ SAFE_CLOSE(fd);
}
static struct tst_test test = {
--
2.45.1
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next reply other threads:[~2026-08-07 13:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 13:05 Disha Goel [this message]
2026-08-07 13:05 ` [LTP] [PATCH 2/2] memcg/memcontrol03-04: fix typos, redundant define and format specifiers Disha Goel
2026-08-07 14:18 ` [LTP] memcg/memcontrol02: fix fd leak in cleanup path linuxtestproject.agent
2026-08-10 9:41 ` Andrea Cervesato via ltp
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=20260807130523.49068-1-disgoel@linux.ibm.com \
--to=disgoel@linux.ibm.com \
--cc=ltp@lists.linux.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.