From: Mateusz Majewski <m.majewski2@samsung.com>
Date: Fri, 25 Aug 2023 10:13:39 +0000 (+0200)
Subject: zlogger: remove outdated comment
X-Git-Tag: accepted/tizen/unified/20230919.091736~4
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=ea7349b960b0475910270bf90eafb0e930026c1d;p=platform%2Fkernel%2Flinux-tizen-modules-source.git

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 <m.majewski2@samsung.com>
---

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);