public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Baokun Li <libaokun1@huawei.com>
To: Ojaswin Mujoo <ojaswin@linux.ibm.com>, Theodore Ts'o <tytso@mit.edu>
Cc: <linux-ext4@vger.kernel.org>, Jan Kara <jack@suse.cz>,
	Ritesh Harjani <ritesh.list@gmail.com>,
	<linux-kernel@vger.kernel.org>, Yang Erkun <yangerkun@huawei.com>
Subject: Re: [PATCH] ext4: cache es->s_journal_inum in ext4_sb_info
Date: Wed, 26 Mar 2025 10:16:31 +0800	[thread overview]
Message-ID: <8b76667a-a331-4bf5-bb6a-8db9319d84da@huawei.com> (raw)
In-Reply-To: <Z-Lunpbeh176mwRu@li-dc0c254c-257c-11b2-a85c-98b6c1322444.ibm.com>

On 2025/3/26 1:57, Ojaswin Mujoo wrote:
> On Tue, Mar 18, 2025 at 10:31:29PM -0400, Theodore Ts'o wrote:
>> On Tue, Mar 18, 2025 at 01:42:31PM +0530, Ojaswin Mujoo wrote:
>>>> So this is something we need to do if the journal is actived, and if
>>>> it's active, then sbi->s_journal will be non-NULL, and so we can just
>>>> check to see if inode == sbi->s_journal instead.  This will simplify
>>> I believe you mean inode == sbi->s_journal->j_inode here right?
>> Yes, that's what I meant; sorry for the not catching this before I
>> sent my reply.
>>
>> Cheers,
>>
>> 					- Ted
> Hi Ted, Baokun,
>
> I got some time to revisit this. Seems like checking against
> s_journal->j_inode is not enough. This is because both
> ext4_check_blockref() and check_block_validity() can be called even
> before journal->j_inode is set:
>
> ext4_open_inode_journal
>    ext4_get_journal_inode
> 	  __ext4_iget
> 		  ext4_ind_check_inode
> 			  ext4_check_blockref  /* j_inode not set */
>
>    journal = jbd2_journal_init_inode
> 	  bmap
> 		  ext4_bmap
> 			 iomap_bmap
> 			   ext4_iomap_begin
> 				   ext4_map_blocks
> 					   check_block_validity
>
>    journal->j_inode = inode
>
>
> Now, I think in this case the best solution might be to use the extra
> field like we do in this patch but set  EXT4_SB(sb)->s_journal_ino
> sufficiently early.
>
> Thoughts?

Because system zone setup happens after the journal are loaded, I think we
can skip the check if the journal haven't been loaded yet, like this:

diff --git a/fs/ext4/inode.c b/fs/ext4/inode.c
index d04d8a7f12e7..38dc72ff7e78 100644
--- a/fs/ext4/inode.c
+++ b/fs/ext4/inode.c
@@ -383,9 +383,10 @@ static int __check_block_validity(struct inode 
*inode, const char *func,
                                 unsigned int line,
                                 struct ext4_map_blocks *map)
  {
+       journal_t *journal = EXT4_SB(inode->i_sb)->s_journal;
+
         if (ext4_has_feature_journal(inode->i_sb) &&
-           (inode->i_ino ==
- le32_to_cpu(EXT4_SB(inode->i_sb)->s_es->s_journal_inum)))
+           (!journal || inode == journal->j_inode))
                 return 0;
         if (!ext4_inode_block_valid(inode, map->m_pblk, map->m_len)) {
                 ext4_error_inode(inode, func, line, map->m_pblk,

If any part of the journal area overlaps with the system zone, we'll catch
it when we add the journal area to the system zone later.


Cheers,
Baokun


  reply	other threads:[~2025-03-26  2:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-14 11:41 [PATCH] ext4: cache es->s_journal_inum in ext4_sb_info Ojaswin Mujoo
2025-03-15  7:19 ` Zhang Yi
2025-03-16  1:41 ` Theodore Ts'o
2025-03-17  3:54   ` Baokun Li
2025-03-18  8:12   ` Ojaswin Mujoo
2025-03-19  2:31     ` Theodore Ts'o
2025-03-25 17:57       ` Ojaswin Mujoo
2025-03-26  2:16         ` Baokun Li [this message]
2025-03-26  4:01           ` Zhang Yi
2025-03-26  6:39             ` Ojaswin Mujoo
2025-03-26  8:33               ` Zhang Yi
2025-03-26  9:26                 ` Baokun Li
2025-03-27  6:20                   ` Ojaswin Mujoo

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=8b76667a-a331-4bf5-bb6a-8db9319d84da@huawei.com \
    --to=libaokun1@huawei.com \
    --cc=jack@suse.cz \
    --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=yangerkun@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