ext4: use ext4_debug() instead of jbd_debug()
authorEric Biggers <ebiggers@kernel.org>
Thu, 5 Jan 2023 07:13:51 +0000 (23:13 -0800)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Thu, 12 Jan 2023 10:59:04 +0000 (11:59 +0100)
commit37914e029bec3cc87c52cdf0384a91ab19cd8b0e
tree4d45247e054e6b2ed9e6ba3f2a7a191cd19250a8
parentb0ed9a032e52a175683d18e2e2e8eec0f9ba1ff9
ext4: use ext4_debug() instead of jbd_debug()

From: Jan Kara <jack@suse.cz>

commit 4978c659e7b5c1926cdb4b556e4ca1fd2de8ad42 upstream.

We use jbd_debug() in some places in ext4. It seems a bit strange to use
jbd2 debugging output function for ext4 code. Also these days
ext4_debug() uses dynamic printk so each debug message can be enabled /
disabled on its own so the time when it made some sense to have these
combined (to allow easier common selecting of messages to report) has
passed. Just convert all jbd_debug() uses in ext4 to ext4_debug().

Signed-off-by: Jan Kara <jack@suse.cz>
Reviewed-by: Lukas Czerner <lczerner@redhat.com>
Link: https://lore.kernel.org/r/20220608112355.4397-1-jack@suse.cz
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Signed-off-by: Eric Biggers <ebiggers@google.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
fs/ext4/balloc.c
fs/ext4/ext4_jbd2.c
fs/ext4/fast_commit.c
fs/ext4/indirect.c
fs/ext4/inode.c
fs/ext4/orphan.c
fs/ext4/super.c