From: patchwork-bot+f2fs@kernel.org
To: Zhiguo Niu <zhiguo.niu@unisoc.com>
Cc: jaegeuk@kernel.org, chao@kernel.org, ke.wang@unisoc.com,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, hongyu.jin@unisoc.com,
niuzhiguo84@gmail.com
Subject: Re: [f2fs-dev] [PATCH v2 0/4] f2fs: fix panic issue in small capacity device
Date: Wed, 21 Feb 2024 18:10:30 +0000 [thread overview]
Message-ID: <170853903087.7043.18353630972928163245.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1707271264-5551-1-git-send-email-zhiguo.niu@unisoc.com>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 7 Feb 2024 10:01:00 +0800 you wrote:
> A panic issue happened in a reboot test in small capacity device
> as following:
> 1.The device size is 64MB, and main area has 24 segments, and
> CONFIG_F2FS_CHECK_FS is not enabled.
> 2.There is no any free segments left shown in free_segmap_info,
> then another write request cause get_new_segment get a out-of-bound
> segment with segno 24.
> 3.panic happen in update_sit_entry because access invalid bitmap
> pointer.
>
> [...]
Here is the summary with links:
- [f2fs-dev,v2,1/4] f2fs: correct counting methods of free_segments in __set_inuse
https://git.kernel.org/jaegeuk/f2fs/c/8bac4167fd14
- [f2fs-dev,v2,2/4] f2fs: fix panic issue in update_sit_entry
https://git.kernel.org/jaegeuk/f2fs/c/4acac2bf18d6
- [f2fs-dev,v2,3/4] f2fs: enhance judgment conditions of GET_SEGNO
(no matching commit)
- [f2fs-dev,v2,4/4] f2fs: stop checkpoint when get a out-of-bounds segment
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-02-21 18:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 2:01 [PATCH v2 0/4] f2fs: fix panic issue in small capacity device Zhiguo Niu
2024-02-07 2:01 ` [PATCH v2 1/4] f2fs: correct counting methods of free_segments in __set_inuse Zhiguo Niu
2024-02-07 2:01 ` [PATCH v2 2/4] f2fs: fix panic issue in update_sit_entry Zhiguo Niu
2024-02-07 2:01 ` [PATCH v2 3/4] f2fs: enhance judgment conditions of GET_SEGNO Zhiguo Niu
2024-02-07 2:01 ` [PATCH v2 4/4] f2fs: stop checkpoint when get a out-of-bounds segment Zhiguo Niu
2024-02-08 0:16 ` Jaegeuk Kim
2024-02-19 7:14 ` Chao Yu
2024-02-21 18:10 ` patchwork-bot+f2fs [this message]
2024-02-22 12:30 ` [PATCH v2 0/4] f2fs: fix panic issue in small capacity device Chao Yu
[not found] ` <CAHJ8P3KYY27M3v=9Lu-yD2ufxU1fdG-bg=G92AbpnLUx0zLz3g@mail.gmail.com>
2024-02-23 2:38 ` Chao Yu
2024-02-26 3:25 ` Zhiguo Niu
2024-02-26 6:48 ` Chao Yu
2024-02-27 1:13 ` Jaegeuk Kim
2024-02-27 2:34 ` Zhiguo Niu
2024-02-27 17:18 ` Jaegeuk Kim
2024-02-28 1:00 ` Zhiguo Niu
2024-02-28 1:21 ` 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=170853903087.7043.18353630972928163245.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=hongyu.jin@unisoc.com \
--cc=jaegeuk@kernel.org \
--cc=ke.wang@unisoc.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=niuzhiguo84@gmail.com \
--cc=zhiguo.niu@unisoc.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