From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: wangzijie <wangzijie1@honor.com>, jaegeuk@kernel.org
Cc: linux-kernel@vger.kernel.org, feng.han@honor.com,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v3 2/2] f2fs: fix infinite loop in __insert_extent_tree()
Date: Wed, 17 Sep 2025 14:48:31 +0800 [thread overview]
Message-ID: <a625f1dd-ec3b-4e2c-9b3f-8a772cdc69dc@kernel.org> (raw)
In-Reply-To: <20250917023622.516052-2-wangzijie1@honor.com>
On 9/17/25 10:36, wangzijie wrote:
> When we get wrong extent info data, and look up extent_node in rb tree,
> it will cause infinite loop (CONFIG_F2FS_CHECK_FS=n). Avoiding this by
> return NULL and print some kernel messages in that case.
>
> Signed-off-by: wangzijie <wangzijie1@honor.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
_______________________________________________
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: wangzijie <wangzijie1@honor.com>, jaegeuk@kernel.org
Cc: chao@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, bintian.wang@honor.com,
feng.han@honor.com
Subject: Re: [f2fs-dev] [PATCH v3 2/2] f2fs: fix infinite loop in __insert_extent_tree()
Date: Wed, 17 Sep 2025 14:48:31 +0800 [thread overview]
Message-ID: <a625f1dd-ec3b-4e2c-9b3f-8a772cdc69dc@kernel.org> (raw)
In-Reply-To: <20250917023622.516052-2-wangzijie1@honor.com>
On 9/17/25 10:36, wangzijie wrote:
> When we get wrong extent info data, and look up extent_node in rb tree,
> it will cause infinite loop (CONFIG_F2FS_CHECK_FS=n). Avoiding this by
> return NULL and print some kernel messages in that case.
>
> Signed-off-by: wangzijie <wangzijie1@honor.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
next prev parent reply other threads:[~2025-09-17 6:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 2:36 [f2fs-dev] [PATCH v3 1/2] f2fs: fix zero-sized extent for precache extents wangzijie
2025-09-17 2:36 ` wangzijie
2025-09-17 2:36 ` [f2fs-dev] [PATCH v3 2/2] f2fs: fix infinite loop in __insert_extent_tree() wangzijie
2025-09-17 2:36 ` wangzijie
2025-09-17 6:48 ` Chao Yu via Linux-f2fs-devel [this message]
2025-09-17 6:48 ` Chao Yu
2025-09-17 6:41 ` [f2fs-dev] [PATCH v3 1/2] f2fs: fix zero-sized extent for precache extents Chao Yu via Linux-f2fs-devel
2025-09-17 6:41 ` Chao Yu
2025-09-17 15:59 ` Jaegeuk Kim via Linux-f2fs-devel
2025-09-17 15:59 ` Jaegeuk Kim
2025-09-29 22:30 ` patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-09-29 22:30 ` 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=a625f1dd-ec3b-4e2c-9b3f-8a772cdc69dc@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=feng.han@honor.com \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wangzijie1@honor.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.