From: Viacheslav Dubeyko <slava@dubeyko.com>
To: Yangtao Li <frank.li@vivo.com>, glaubitz@physik.fu-berlin.de
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hfs: export dbg_flags in debugfs
Date: Fri, 09 May 2025 10:39:12 -0700 [thread overview]
Message-ID: <e87e0fce1391a34ccd3f62581f8dc62d03b5c022.camel@dubeyko.com> (raw)
In-Reply-To: <20250507145550.425303-1-frank.li@vivo.com>
Hi Yangtao,
On Wed, 2025-05-07 at 08:55 -0600, Yangtao Li wrote:
> hfs currently has some function tracking points,
> which are helpful for problem analysis, but rely on
> modifying the DBG_MASK macro.
>
> Modifying the macro requires recompiling the kernel,
> and the control of the log is more troublesome.
>
> Let's export this debug facility to debugfs so that
> it can be easily controlled through the node.
>
> node:
> /sys/kernel/debug/hfs/dbg_flags
>
> for_each_bit:
>
> DBG_BNODE_REFS 0x00000001
> DBG_BNODE_MOD 0x00000002
> DBG_CAT_MOD 0x00000004
> DBG_INODE 0x00000008
> DBG_SUPER 0x00000010
> DBG_EXTENT 0x00000020
> DBG_BITMAP 0x00000040
>
Frankly speaking, if we would like to rework the debugging framework in
HFS/HFS+, then I prefer to switch on pr_debug() and to use dynamic
debug framework of Linux kernel [1]. It will provide the more flexible
solution.
Thanks,
Slava.
[1] https://www.kernel.org/doc/html/v4.14/admin-guide/dynamic-debug-howto.html
next prev parent reply other threads:[~2025-05-09 17:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 14:55 Yangtao Li
2025-05-08 13:26 ` kernel test robot
2025-05-09 17:39 ` Viacheslav Dubeyko [this message]
2025-05-11 10:45 ` 回复: " 李扬韬
2025-05-15 1:22 ` Viacheslav Dubeyko
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=e87e0fce1391a34ccd3f62581f8dc62d03b5c022.camel@dubeyko.com \
--to=slava@dubeyko.com \
--cc=frank.li@vivo.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®