All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Jaegeuk Kim <jaegeuk@kernel.org>, g@google.com
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/2] f2fs: add f2fs_bug_on() to detect potential bug
Date: Tue, 13 May 2025 10:44:53 +0800	[thread overview]
Message-ID: <2a6bb772-901a-4054-80fa-7ff7cb118944@kernel.org> (raw)
In-Reply-To: <aCITHczkYs49uBSc@google.com>

On 5/12/25 23:26, Jaegeuk Kim wrote:
> On 05/12, Chao Yu wrote:
>> Add f2fs_bug_on() to check whether memory preallocation will fail or
>> not after radix_tree_preload(GFP_NOFS | __GFP_NOFAIL).
> 
> Are we getting a bug?

No, I'm worried about potential issue from add_free_nid() can cause
node footer corruption issue, so I want to use f2fs_bug_on() to check
whether there is caused by any bug from MM from now on.

Thanks,

> 
>>
>> Signed-off-by: Chao Yu <chao@kernel.org>
>> ---
>>  fs/f2fs/checkpoint.c | 4 +++-
>>  fs/f2fs/node.c       | 7 +++++--
>>  2 files changed, 8 insertions(+), 3 deletions(-)
>>
>> diff --git a/fs/f2fs/checkpoint.c b/fs/f2fs/checkpoint.c
>> index e7907858eb70..3f223bade520 100644
>> --- a/fs/f2fs/checkpoint.c
>> +++ b/fs/f2fs/checkpoint.c
>> @@ -504,6 +504,7 @@ static void __add_ino_entry(struct f2fs_sb_info *sbi, nid_t ino,
>>  {
>>  	struct inode_management *im = &sbi->im[type];
>>  	struct ino_entry *e = NULL, *new = NULL;
>> +	int ret;
>>  
>>  	if (type == FLUSH_INO) {
>>  		rcu_read_lock();
>> @@ -516,7 +517,8 @@ static void __add_ino_entry(struct f2fs_sb_info *sbi, nid_t ino,
>>  		new = f2fs_kmem_cache_alloc(ino_entry_slab,
>>  						GFP_NOFS, true, NULL);
>>  
>> -	radix_tree_preload(GFP_NOFS | __GFP_NOFAIL);
>> +	ret = radix_tree_preload(GFP_NOFS | __GFP_NOFAIL);
>> +	f2fs_bug_on(sbi, ret);
>>  
>>  	spin_lock(&im->ino_lock);
>>  	e = radix_tree_lookup(&im->ino_root, ino);
>> diff --git a/fs/f2fs/node.c b/fs/f2fs/node.c
>> index 3f6b8037d25f..88d3032236cb 100644
>> --- a/fs/f2fs/node.c
>> +++ b/fs/f2fs/node.c
>> @@ -2309,7 +2309,7 @@ static bool add_free_nid(struct f2fs_sb_info *sbi,
>>  	struct f2fs_nm_info *nm_i = NM_I(sbi);
>>  	struct free_nid *i, *e;
>>  	struct nat_entry *ne;
>> -	int err = -EINVAL;
>> +	int err;
>>  	bool ret = false;
>>  
>>  	/* 0 nid should not be used */
>> @@ -2323,7 +2323,10 @@ static bool add_free_nid(struct f2fs_sb_info *sbi,
>>  	i->nid = nid;
>>  	i->state = FREE_NID;
>>  
>> -	radix_tree_preload(GFP_NOFS | __GFP_NOFAIL);
>> +	err = radix_tree_preload(GFP_NOFS | __GFP_NOFAIL);
>> +	f2fs_bug_on(sbi, err);
>> +
>> +	err = -EINVAL;
>>  
>>  	spin_lock(&nm_i->nid_list_lock);
>>  
>> -- 
>> 2.49.0



_______________________________________________
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: Jaegeuk Kim <jaegeuk@kernel.org>, g@google.com
Cc: chao@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] f2fs: add f2fs_bug_on() to detect potential bug
Date: Tue, 13 May 2025 10:44:53 +0800	[thread overview]
Message-ID: <2a6bb772-901a-4054-80fa-7ff7cb118944@kernel.org> (raw)
In-Reply-To: <aCITHczkYs49uBSc@google.com>

On 5/12/25 23:26, Jaegeuk Kim wrote:
> On 05/12, Chao Yu wrote:
>> Add f2fs_bug_on() to check whether memory preallocation will fail or
>> not after radix_tree_preload(GFP_NOFS | __GFP_NOFAIL).
> 
> Are we getting a bug?

No, I'm worried about potential issue from add_free_nid() can cause
node footer corruption issue, so I want to use f2fs_bug_on() to check
whether there is caused by any bug from MM from now on.

Thanks,

> 
>>
>> Signed-off-by: Chao Yu <chao@kernel.org>
>> ---
>>  fs/f2fs/checkpoint.c | 4 +++-
>>  fs/f2fs/node.c       | 7 +++++--
>>  2 files changed, 8 insertions(+), 3 deletions(-)
>>
>> diff --git a/fs/f2fs/checkpoint.c b/fs/f2fs/checkpoint.c
>> index e7907858eb70..3f223bade520 100644
>> --- a/fs/f2fs/checkpoint.c
>> +++ b/fs/f2fs/checkpoint.c
>> @@ -504,6 +504,7 @@ static void __add_ino_entry(struct f2fs_sb_info *sbi, nid_t ino,
>>  {
>>  	struct inode_management *im = &sbi->im[type];
>>  	struct ino_entry *e = NULL, *new = NULL;
>> +	int ret;
>>  
>>  	if (type == FLUSH_INO) {
>>  		rcu_read_lock();
>> @@ -516,7 +517,8 @@ static void __add_ino_entry(struct f2fs_sb_info *sbi, nid_t ino,
>>  		new = f2fs_kmem_cache_alloc(ino_entry_slab,
>>  						GFP_NOFS, true, NULL);
>>  
>> -	radix_tree_preload(GFP_NOFS | __GFP_NOFAIL);
>> +	ret = radix_tree_preload(GFP_NOFS | __GFP_NOFAIL);
>> +	f2fs_bug_on(sbi, ret);
>>  
>>  	spin_lock(&im->ino_lock);
>>  	e = radix_tree_lookup(&im->ino_root, ino);
>> diff --git a/fs/f2fs/node.c b/fs/f2fs/node.c
>> index 3f6b8037d25f..88d3032236cb 100644
>> --- a/fs/f2fs/node.c
>> +++ b/fs/f2fs/node.c
>> @@ -2309,7 +2309,7 @@ static bool add_free_nid(struct f2fs_sb_info *sbi,
>>  	struct f2fs_nm_info *nm_i = NM_I(sbi);
>>  	struct free_nid *i, *e;
>>  	struct nat_entry *ne;
>> -	int err = -EINVAL;
>> +	int err;
>>  	bool ret = false;
>>  
>>  	/* 0 nid should not be used */
>> @@ -2323,7 +2323,10 @@ static bool add_free_nid(struct f2fs_sb_info *sbi,
>>  	i->nid = nid;
>>  	i->state = FREE_NID;
>>  
>> -	radix_tree_preload(GFP_NOFS | __GFP_NOFAIL);
>> +	err = radix_tree_preload(GFP_NOFS | __GFP_NOFAIL);
>> +	f2fs_bug_on(sbi, err);
>> +
>> +	err = -EINVAL;
>>  
>>  	spin_lock(&nm_i->nid_list_lock);
>>  
>> -- 
>> 2.49.0


  reply	other threads:[~2025-05-13  2:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-12 11:54 [f2fs-dev] [PATCH 1/2] f2fs: add f2fs_bug_on() to detect potential bug Chao Yu via Linux-f2fs-devel
2025-05-12 11:54 ` Chao Yu
2025-05-12 11:54 ` [f2fs-dev] [PATCH 2/2] f2fs: add f2fs_bug_on() in f2fs_quota_read() Chao Yu via Linux-f2fs-devel
2025-05-12 11:54   ` Chao Yu
2025-05-12 15:27   ` [f2fs-dev] " Jaegeuk Kim via Linux-f2fs-devel
2025-05-12 15:27     ` Jaegeuk Kim
2025-05-13  2:45     ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2025-05-13  2:45       ` Chao Yu
2025-05-12 15:26 ` [f2fs-dev] [PATCH 1/2] f2fs: add f2fs_bug_on() to detect potential bug Jaegeuk Kim via Linux-f2fs-devel
2025-05-12 15:26   ` Jaegeuk Kim
2025-05-13  2:44   ` Chao Yu via Linux-f2fs-devel [this message]
2025-05-13  2:44     ` Chao Yu
2025-05-14 15:40 ` [f2fs-dev] " patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-05-14 15:40   ` patchwork-bot+f2fs

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=2a6bb772-901a-4054-80fa-7ff7cb118944@kernel.org \
    --to=linux-f2fs-devel@lists.sourceforge.net \
    --cc=chao@kernel.org \
    --cc=g@google.com \
    --cc=jaegeuk@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 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.