Currently mkfs/fsck gets the following error when executed by
non-root users:
Info: open /dev/loop0 failed errno:13
Error: Not available on mounted device!
Let's fix it by reading the backing file from sysfs.
Fixes: 14197d546b93 ("f2fs-tools: fix to check loop device")
Signed-off-by: Hua
Currently mkfs/fsck gets the following error when executed by
non-root users:
Info: open /dev/loop0 failed errno:13
Error: Not available on mounted device!
Let's fix it by reading the backing file from sysfs.
Fixes: 14197d546b93 ("f2fs-tools: fix to check loop device")
Signed-off-by: Hua
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim :
On Fri, 23 Feb 2024 12:55:31 -0800 you wrote:
> In cfd66bb715fd ("f2fs: fix deadloop in foreground GC"), we needed to check
> the number of blocks in a section instead of the segment.
>
> In addtion, let's check the entire
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim :
On Thu, 22 Feb 2024 20:18:48 +0800 you wrote:
> Commit 093749e296e2 ("f2fs: support age threshold based garbage
> collection") added this declaration, but w/ definition, delete
> it.
>
> Signed-off-by: Chao Yu
> ---
> fs
Hello:
The following patches were marked "accepted", because they were applied to
jaegeuk/f2fs.git (dev):
Series: [f2fs-dev,1/5] f2fs: check number of blocks in a current section
Submitter: Jaegeuk Kim
Patchwork: https://patchwork.kernel.org/project/f2fs/list/?series=829303
Lore link:
htt
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim :
On Mon, 19 Feb 2024 10:28:44 +0800 you wrote:
> It needs to check compress flag w/ .i_sem lock, otherwise, compressed
> inode may be disabled after the check condition, it's not needed to
> set compress option on non-compres
On Wed, Feb 28, 2024 at 7:09 PM Shinichiro Kawasaki
wrote:
>
> On Feb 19, 2024 / 00:58, Yi Zhang wrote:
> > Hello
> > I reproduced this issue on the latest linux-block/for-next, please
> > help check it and let me know if you need more info/test, thanks.
>
> [...]
>
> > [ 4381.278858]
If GET_SEGNO return NULL_SEGNO for some unecpected case,
update_sit_entry will access invalid memory address,
cause system crash. It is better to do sanity check about
GET_SEGNO just like update_segment_mtime & locate_dirty_segment.
Also remove some redundant judgment code.
Signed-off-by: Zhiguo
On Feb 19, 2024 / 00:58, Yi Zhang wrote:
> Hello
> I reproduced this issue on the latest linux-block/for-next, please
> help check it and let me know if you need more info/test, thanks.
[...]
> [ 4381.278858] [ cut here ]
> [ 4381.283484] WARNING: CPU: 22 PID: 44011 at fs/
