From ea7349b960b0475910270bf90eafb0e930026c1d Mon Sep 17 00:00:00 2001 From: Mateusz Majewski Date: Fri, 25 Aug 2023 12:13:39 +0200 Subject: [PATCH] zlogger: remove outdated comment The comment isn't outright false, as the userspace might really be using the block. However, 3a489d20b218eec5073f18e5b248ced6c6a843d8 handles exactly that case, so it is completely normal and correct to unmap the block that is in use. Change-Id: Icc4bec0268a3cba23990e35fb36448851ca4fb1f Signed-off-by: Mateusz Majewski --- kernel/zlogger/zlogger.c | 1 - 1 file changed, 1 deletion(-) diff --git a/kernel/zlogger/zlogger.c b/kernel/zlogger/zlogger.c index 427ebf6..1c047a9 100644 --- a/kernel/zlogger/zlogger.c +++ b/kernel/zlogger/zlogger.c @@ -262,7 +262,6 @@ static int zlog_task(void *user_data) if (blk && get_block(blk)->head.ts < g_start_time) { get_block(blk)->head.tid = 0; ptr->blk = 0; - // TODO: The userspace might very well be using this block right now. zlogger_unmap(ptr); mutex_lock(&g_block_mutex); queue_push(&g_free_q, blk); -- 2.34.1