linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Capitulino <luizcap@redhat.com>
To: catalin.marinas@arm.com
Cc: lcapitulino@gmail.com, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, david@redhat.com
Subject: [PATCH 2/3] mm: kmemleak: drop wrong comment
Date: Wed, 30 Apr 2025 16:59:46 -0400	[thread overview]
Message-ID: <3dfd09bc0e77bb626619184a808774ff07de275c.1746046744.git.luizcap@redhat.com> (raw)
In-Reply-To: <cover.1746046744.git.luizcap@redhat.com>

Newly created objects have object->count == 0, so the comment is
incorrect. Just drop it.

Signed-off-by: Luiz Capitulino <luizcap@redhat.com>
---
 mm/kmemleak.c | 2 --
 1 file changed, 2 deletions(-)

diff --git a/mm/kmemleak.c b/mm/kmemleak.c
index e6df94c7b032..06baa3475252 100644
--- a/mm/kmemleak.c
+++ b/mm/kmemleak.c
@@ -322,8 +322,6 @@ static void hex_dump_object(struct seq_file *seq,
  *		sufficient references to it (count >= min_count)
  * - black - ignore, it doesn't contain references (e.g. text section)
  *		(min_count == -1). No function defined for this color.
- * Newly created objects don't have any color assigned (object->count == -1)
- * before the next memory scan when they become white.
  */
 static bool color_white(const struct kmemleak_object *object)
 {
-- 
2.49.0



  parent reply	other threads:[~2025-04-30 21:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-30 20:59 [PATCH 0/3] mm: kmemleak: small cleanup Luiz Capitulino
2025-04-30 20:59 ` [PATCH 1/3] mm: kmemleak: drop kmemleak_warning variable Luiz Capitulino
2025-05-01 10:39   ` Catalin Marinas
2025-04-30 20:59 ` Luiz Capitulino [this message]
2025-05-01 10:40   ` [PATCH 2/3] mm: kmemleak: drop wrong comment Catalin Marinas
2025-04-30 20:59 ` [PATCH 3/3] mm: kmemleak: mark variables as __read_mostly Luiz Capitulino
2025-05-01 10:42   ` Catalin Marinas
2025-04-30 21:06 ` [PATCH 0/3] mm: kmemleak: small cleanup David Hildenbrand

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=3dfd09bc0e77bb626619184a808774ff07de275c.1746046744.git.luizcap@redhat.com \
    --to=luizcap@redhat.com \
    --cc=catalin.marinas@arm.com \
    --cc=david@redhat.com \
    --cc=lcapitulino@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    /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