[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id:
<170853903087.7043.18353630972928163245.git-patchwork-notify@kernel.org>
Date: Wed, 21 Feb 2024 18:10:30 +0000
From: patchwork-bot+f2fs@...nel.org
To: Zhiguo Niu <zhiguo.niu@...soc.com>
Cc: jaegeuk@...nel.org, chao@...nel.org, ke.wang@...soc.com,
linux-kernel@...r.kernel.org, linux-f2fs-devel@...ts.sourceforge.net,
hongyu.jin@...soc.com, niuzhiguo84@...il.com
Subject: Re: [f2fs-dev] [PATCH v2 0/4] f2fs: fix panic issue in small capacity
device
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@...nel.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
Powered by blists - more mailing lists