mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: lirongqing <lirongqing@baidu.com>
To: Theodore Ts'o <tytso@mit.edu>,
	Andreas Dilger <adilger.kernel@dilger.ca>,
	Baokun Li <libaokun@linux.alibaba.com>, Jan Kara <jack@suse.cz>,
	Ojaswin Mujoo <ojaswin@linux.ibm.com>,
	Ritesh Harjani <ritesh.list@gmail.com>,
	Zhang Yi <yi.zhang@huawei.com>, <linux-ext4@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Cc: Li RongQing <lirongqing@baidu.com>
Subject: [PATCH] ext4: convert legacy ext4_debug() to standard pr_debug()
Date: Thu, 21 May 2026 03:46:34 -0400	[thread overview]
Message-ID: <20260521074634.2697-1-lirongqing@baidu.com> (raw)

From: Li RongQing <lirongqing@baidu.com>

The ext4 file system historically implemented its own debug logging macro
ext4_debug() via EXT4FS_DEBUG conditional compilation. This legacy
implementation suffers from two major drawbacks:

1. It makes two consecutive un-serialized printk() calls, which can
   lead to severe log interleaving and corruption under multi-core
   concurrent workloads.
2. It completely bypasses the standard modern kernel dynamic debug
   (CONFIG_DYNAMIC_DEBUG) infrastructure.

Clean up the legacy implementation by leveraging pr_debug(). This squashes
the multiple printk() calls into a single atomic execution, ensuring
log integrity, while seamlessly hooking ext4 into the kernel's native
dynamic debug framework.

The redundant __FILE__ and __LINE__ macros are intentionally removed from
the string format because the dynamic debug infrastructure can already
append them automatically at runtime (via the '+fl' flags) if desired.
This avoids redundancy and double-logging in modern production/debugging
environments while keeping the macro clean and robust against dangling
comma compiler errors.

Signed-off-by: Li RongQing <lirongqing@baidu.com>
---
 fs/ext4/ext4.h | 20 ++------------------
 1 file changed, 2 insertions(+), 18 deletions(-)

diff --git a/fs/ext4/ext4.h b/fs/ext4/ext4.h
index 94283a9..39e86ff 100644
--- a/fs/ext4/ext4.h
+++ b/fs/ext4/ext4.h
@@ -62,24 +62,8 @@
  */
 #define DOUBLE_CHECK__
 
-/*
- * Define EXT4FS_DEBUG to produce debug messages
- */
-#undef EXT4FS_DEBUG
-
-/*
- * Debug code
- */
-#ifdef EXT4FS_DEBUG
-#define ext4_debug(f, a...)						\
-	do {								\
-		printk(KERN_DEBUG "EXT4-fs DEBUG (%s, %d): %s:",	\
-			__FILE__, __LINE__, __func__);			\
-		printk(KERN_DEBUG f, ## a);				\
-	} while (0)
-#else
-#define ext4_debug(fmt, ...)	no_printk(fmt, ##__VA_ARGS__)
-#endif
+#define ext4_debug(fmt, ...)						\
+	pr_debug("EXT4-fs DEBUG %s: " fmt, __func__,  ##__VA_ARGS__)
 
  /*
   * Turn on EXT_DEBUG to enable ext4_ext_show_path/leaf/move in extents.c
-- 
2.9.4


             reply	other threads:[~2026-05-21  7:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-21  7:46 lirongqing [this message]
2026-05-25 15:16 ` Jan Kara
2026-05-29  7:32 ` Baokun Li

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=20260521074634.2697-1-lirongqing@baidu.com \
    --to=lirongqing@baidu.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=jack@suse.cz \
    --cc=libaokun@linux.alibaba.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ojaswin@linux.ibm.com \
    --cc=ritesh.list@gmail.com \
    --cc=tytso@mit.edu \
    --cc=yi.zhang@huawei.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

all inboxes | Powered by JetHome®