[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20241107144538.3544-1-dalme@riseup.net>
Date: Thu, 7 Nov 2024 15:45:38 +0100
From: Daniel Martín Gómez <dalme@...eup.net>
To:
Cc: dalme@...eup.net,
"Theodore Ts'o" <tytso@....edu>,
Jan Kara <jack@...e.com>,
linux-ext4@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: [PATCH] jbd2: Fix comment describing journal_init_common()
The code indicates that journal_init_common() fills the journal_t object
it returns while the comment incorrectly states that only a few fields are
initialised. Also, the comment claims that journal structures could be
created from scratch which isn't possible as journal_init_common() calls
journal_load_superblock() which loads and checks journal superblock from
disk.
Signed-off-by: Daniel Martín Gómez <dalme@...eup.net>
---
fs/jbd2/journal.c | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/fs/jbd2/journal.c b/fs/jbd2/journal.c
index 97f487c3d8fc..3c1d42133687 100644
--- a/fs/jbd2/journal.c
+++ b/fs/jbd2/journal.c
@@ -1518,9 +1518,10 @@ static int journal_load_superblock(journal_t *journal)
* destroy journal_t structures, and to initialise and read existing
* journal blocks from disk. */
-/* First: create and setup a journal_t object in memory. We initialise
- * very few fields yet: that has to wait until we have created the
- * journal structures from from scratch, or loaded them from disk. */
+/* The journal_init_common() function creates and fills a journal_t object
+ * in memory. It calls journal_load_superblock() to load the on-disk journal
+ * superblock and initialize the journal_t object.
+ */
static journal_t *journal_init_common(struct block_device *bdev,
struct block_device *fs_dev,
--
2.39.5
Powered by blists - more mailing lists