All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Deepanshu Kartikey <kartikey406@gmail.com>, jaegeuk@kernel.org
Cc: stable@kernel.org,
	syzbot+eec8f2693d71386bd600@syzkaller.appspotmail.com,
	linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: initialize ino_entry_info before checkpoint load
Date: Mon, 22 Jun 2026 08:59:51 +0800	[thread overview]
Message-ID: <f8f1d255-3f45-43c8-bf7d-e9b12401e8b3@kernel.org> (raw)
In-Reply-To: <CADhLXY57Oi+5+1PNb3ywnfVFV3iCHd-OFmpBS0=ooq0nFuKxiA@mail.gmail.com>

On 6/21/26 16:18, Deepanshu Kartikey wrote:
> On Sun, May 10, 2026 at 9:53 AM Deepanshu Kartikey
> <kartikey406@gmail.com> wrote:
>>
>> When f2fs_get_valid_checkpoint() fails during mount (e.g. due to an
>> invalid checkpoint CRC on a malformed image), f2fs_fill_super() takes
>> an error path that eventually calls iput() on the root inode. This
>> invokes f2fs_drop_inode() -> f2fs_exist_written_data(), which acquires
>> sbi->im[]->ino_lock. However, f2fs_init_ino_entry_info() has not run
>> yet at this point, so the spinlock is uninitialized and lockdep
>> complains:
>>
>>    F2FS-fs (loop0): invalid crc value
>>    F2FS-fs (loop0): Failed to get valid F2FS checkpoint
>>    INFO: trying to register non-static key.
>>    The code is fine but needs lockdep annotation, or maybe
>>    you didn't initialize this object before use?
>>    ...
>>     f2fs_exist_written_data+0x53/0x90 fs/f2fs/checkpoint.c:787
>>     f2fs_drop_inode+0xda/0xbf0 fs/f2fs/super.c:1852
>>     iput+0x651/0xe80 fs/inode.c:2009
>>     f2fs_fill_super+0x6047/0x7850 fs/f2fs/super.c:5461
>>
>> Move f2fs_init_ino_entry_info() to before f2fs_get_valid_checkpoint()
>> so that sbi->im[] is always fully initialized before any error path
>> can trigger iput() -> f2fs_drop_inode(). The init function only
>> depends on raw superblock fields (BLKS_PER_SEG, F2FS_CP_PACKS,
>> NR_CURSEG_PERSIST_TYPE, __cp_payload), which are populated well
>> before checkpoint load, so the move is safe.
>>
>> Fixes: 3063c80776e3 ("f2fs: another way to set large folio by remembering inode number")
>> Cc: stable@kernel.org
>> Reported-by: syzbot+eec8f2693d71386bd600@syzkaller.appspotmail.com
>> Closes: https://syzkaller.appspot.com/bug?extid=eec8f2693d71386bd600
>> Tested-by: syzbot+eec8f2693d71386bd600@syzkaller.appspotmail.com
>> Signed-off-by: Deepanshu Kartikey <kartikey406@gmail.com>
>> ---
>> Changes in v2:
>>   - Add Fixes: tag (suggested by Chao Yu)
>>   - Add Cc: stable@kernel.org
>> ---
>>   fs/f2fs/super.c | 9 +++++++--
>>   1 file changed, 7 insertions(+), 2 deletions(-)
>>
>> diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c
>> index c6afdbd6e1cd..6a231a5b0d62 100644
>> --- a/fs/f2fs/super.c
>> +++ b/fs/f2fs/super.c
>> @@ -5140,6 +5140,13 @@ static int f2fs_fill_super(struct super_block *sb, struct fs_context *fc)
>>                  goto free_page_array_cache;
>>          }
>>
>> +       /*
>> +        * Initialize ino entry info early so f2fs_drop_inode ->
>> +        * f2fs_exist_written_data can safely take im->ino_lock if mount
>> +        * fails after this point and triggers iput on cleanup.
>> +        */
>> +       f2fs_init_ino_entry_info(sbi);
>> +
>>          err = f2fs_get_valid_checkpoint(sbi);
>>          if (err) {
>>                  f2fs_err(sbi, "Failed to get valid F2FS checkpoint");
>> @@ -5184,8 +5191,6 @@ static int f2fs_fill_super(struct super_block *sb, struct fs_context *fc)
>>
>>          f2fs_init_extent_cache_info(sbi);
>>
>> -       f2fs_init_ino_entry_info(sbi);
>> -
>>          f2fs_init_fsync_node_info(sbi);
>>
>>          /* setup checkpoint request control and start checkpoint issue thread */
>> --
>> 2.43.0
>>
> 
> Hi Chao,
> 
> Please let me know the status of this patch. This is already "Reviewed-by:" you.

https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git/commit/?h=dev-test&id=065a6f8cd23a9297b543dcec913feb3cb787a25e

It was merged, however, I think it should be reverted because commit 3063c80776e3
("f2fs: another way to set large folio by remembering inode number") was removed
from dev branch, we won't call f2fs_exist_written_data() from f2fs_drop_inode().

Thanks,

> 
> Please let me know if anything needed from my side.
> 
> Thanks
> 
> Deepanshu Kartikey



_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

WARNING: multiple messages have this Message-ID (diff)
From: Chao Yu <chao@kernel.org>
To: Deepanshu Kartikey <kartikey406@gmail.com>, jaegeuk@kernel.org
Cc: chao@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, stable@kernel.org,
	syzbot+eec8f2693d71386bd600@syzkaller.appspotmail.com
Subject: Re: [PATCH v2] f2fs: initialize ino_entry_info before checkpoint load
Date: Mon, 22 Jun 2026 08:59:51 +0800	[thread overview]
Message-ID: <f8f1d255-3f45-43c8-bf7d-e9b12401e8b3@kernel.org> (raw)
In-Reply-To: <CADhLXY57Oi+5+1PNb3ywnfVFV3iCHd-OFmpBS0=ooq0nFuKxiA@mail.gmail.com>

On 6/21/26 16:18, Deepanshu Kartikey wrote:
> On Sun, May 10, 2026 at 9:53 AM Deepanshu Kartikey
> <kartikey406@gmail.com> wrote:
>>
>> When f2fs_get_valid_checkpoint() fails during mount (e.g. due to an
>> invalid checkpoint CRC on a malformed image), f2fs_fill_super() takes
>> an error path that eventually calls iput() on the root inode. This
>> invokes f2fs_drop_inode() -> f2fs_exist_written_data(), which acquires
>> sbi->im[]->ino_lock. However, f2fs_init_ino_entry_info() has not run
>> yet at this point, so the spinlock is uninitialized and lockdep
>> complains:
>>
>>    F2FS-fs (loop0): invalid crc value
>>    F2FS-fs (loop0): Failed to get valid F2FS checkpoint
>>    INFO: trying to register non-static key.
>>    The code is fine but needs lockdep annotation, or maybe
>>    you didn't initialize this object before use?
>>    ...
>>     f2fs_exist_written_data+0x53/0x90 fs/f2fs/checkpoint.c:787
>>     f2fs_drop_inode+0xda/0xbf0 fs/f2fs/super.c:1852
>>     iput+0x651/0xe80 fs/inode.c:2009
>>     f2fs_fill_super+0x6047/0x7850 fs/f2fs/super.c:5461
>>
>> Move f2fs_init_ino_entry_info() to before f2fs_get_valid_checkpoint()
>> so that sbi->im[] is always fully initialized before any error path
>> can trigger iput() -> f2fs_drop_inode(). The init function only
>> depends on raw superblock fields (BLKS_PER_SEG, F2FS_CP_PACKS,
>> NR_CURSEG_PERSIST_TYPE, __cp_payload), which are populated well
>> before checkpoint load, so the move is safe.
>>
>> Fixes: 3063c80776e3 ("f2fs: another way to set large folio by remembering inode number")
>> Cc: stable@kernel.org
>> Reported-by: syzbot+eec8f2693d71386bd600@syzkaller.appspotmail.com
>> Closes: https://syzkaller.appspot.com/bug?extid=eec8f2693d71386bd600
>> Tested-by: syzbot+eec8f2693d71386bd600@syzkaller.appspotmail.com
>> Signed-off-by: Deepanshu Kartikey <kartikey406@gmail.com>
>> ---
>> Changes in v2:
>>   - Add Fixes: tag (suggested by Chao Yu)
>>   - Add Cc: stable@kernel.org
>> ---
>>   fs/f2fs/super.c | 9 +++++++--
>>   1 file changed, 7 insertions(+), 2 deletions(-)
>>
>> diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c
>> index c6afdbd6e1cd..6a231a5b0d62 100644
>> --- a/fs/f2fs/super.c
>> +++ b/fs/f2fs/super.c
>> @@ -5140,6 +5140,13 @@ static int f2fs_fill_super(struct super_block *sb, struct fs_context *fc)
>>                  goto free_page_array_cache;
>>          }
>>
>> +       /*
>> +        * Initialize ino entry info early so f2fs_drop_inode ->
>> +        * f2fs_exist_written_data can safely take im->ino_lock if mount
>> +        * fails after this point and triggers iput on cleanup.
>> +        */
>> +       f2fs_init_ino_entry_info(sbi);
>> +
>>          err = f2fs_get_valid_checkpoint(sbi);
>>          if (err) {
>>                  f2fs_err(sbi, "Failed to get valid F2FS checkpoint");
>> @@ -5184,8 +5191,6 @@ static int f2fs_fill_super(struct super_block *sb, struct fs_context *fc)
>>
>>          f2fs_init_extent_cache_info(sbi);
>>
>> -       f2fs_init_ino_entry_info(sbi);
>> -
>>          f2fs_init_fsync_node_info(sbi);
>>
>>          /* setup checkpoint request control and start checkpoint issue thread */
>> --
>> 2.43.0
>>
> 
> Hi Chao,
> 
> Please let me know the status of this patch. This is already "Reviewed-by:" you.

https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git/commit/?h=dev-test&id=065a6f8cd23a9297b543dcec913feb3cb787a25e

It was merged, however, I think it should be reverted because commit 3063c80776e3
("f2fs: another way to set large folio by remembering inode number") was removed
from dev branch, we won't call f2fs_exist_written_data() from f2fs_drop_inode().

Thanks,

> 
> Please let me know if anything needed from my side.
> 
> Thanks
> 
> Deepanshu Kartikey


  reply	other threads:[~2026-06-22  1:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-10  4:23 [f2fs-dev] [PATCH v2] f2fs: initialize ino_entry_info before checkpoint load Deepanshu Kartikey
2026-05-10  4:23 ` Deepanshu Kartikey
2026-05-11  1:41 ` [f2fs-dev] " patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-05-11  1:41   ` patchwork-bot+f2fs
2026-05-17  9:22 ` Chao Yu via Linux-f2fs-devel
2026-05-17  9:22   ` Chao Yu
2026-06-21  8:18 ` [f2fs-dev] " Deepanshu Kartikey
2026-06-21  8:18   ` Deepanshu Kartikey
2026-06-22  0:59   ` Chao Yu via Linux-f2fs-devel [this message]
2026-06-22  0:59     ` Chao Yu

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=f8f1d255-3f45-43c8-bf7d-e9b12401e8b3@kernel.org \
    --to=linux-f2fs-devel@lists.sourceforge.net \
    --cc=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=kartikey406@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@kernel.org \
    --cc=syzbot+eec8f2693d71386bd600@syzkaller.appspotmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.