Re: [f2fs-dev] [PATCH v6] f2fs: support FAULT_LOCK type fault injection

On 2023/4/20 14:22, Yangtao Li wrote: Similar to FAULT_LOCK_OP, this patch supports to inject fault into variant of _trylock(), including: - inode_trylock - down_read_trylock - down_write_trylock - mutex_trylock - sb_start_write_trylock - trylock_page Usage: a) echo 524288

Re: [f2fs-dev] [PATCH v6] f2fs: support FAULT_LOCK type fault injection

ping.. ___ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

[f2fs-dev] [PATCH v6] f2fs: support FAULT_LOCK type fault injection

Similar to FAULT_LOCK_OP, this patch supports to inject fault into variant of _trylock(), including: - inode_trylock - down_read_trylock - down_write_trylock - mutex_trylock - sb_start_write_trylock - trylock_page Usage: a) echo 524288 > /sys/fs/f2fs//inject_type or b) mount -o

Re: [f2fs-dev] [PATCH v6] f2fs: support errors=remount-ro|continue|panic mountoption

On 11/14, Chao Yu wrote: > On 2022/11/8 9:17, Chao Yu wrote: > > Jaegeuk, > > > > On 2022/11/8 5:49, Jaegeuk Kim wrote: > > > Chao, > > > > > > Could you please run xfstests since I met some issues with this? > > > I had to drop this to test other patches. > > > > Oops, I ran xfstests on v5, I

Re: [f2fs-dev] [PATCH v6] f2fs: support errors=remount-ro|continue|panic mountoption

On 2022/11/8 9:17, Chao Yu wrote: Jaegeuk, On 2022/11/8 5:49, Jaegeuk Kim wrote: Chao, Could you please run xfstests since I met some issues with this? I had to drop this to test other patches. Oops, I ran xfstests on v5, I didn't see any issus... and in v6 I just rebase codes on ("f2fs:

Re: [f2fs-dev] [PATCH v6] f2fs: support errors=remount-ro|continue|panic mountoption

Jaegeuk, On 2022/11/8 5:49, Jaegeuk Kim wrote: Chao, Could you please run xfstests since I met some issues with this? I had to drop this to test other patches. Oops, I ran xfstests on v5, I didn't see any issus... and in v6 I just rebase codes on ("f2fs: fix to avoid accessing uninitialized

Re: [f2fs-dev] [PATCH v6] f2fs: support errors=remount-ro|continue|panic mountoption

Chao, Could you please run xfstests since I met some issues with this? I had to drop this to test other patches. Thanks, On 11/06, Chao Yu wrote: > This patch supports errors=remount-ro|continue|panic mount option. > > Signed-off-by: Chao Yu > Signed-off-by: Yangtao Li > Signed-off-by:

[f2fs-dev] [PATCH v6] f2fs: support errors=remount-ro|continue|panic mountoption

This patch supports errors=remount-ro|continue|panic mount option. Signed-off-by: Chao Yu Signed-off-by: Yangtao Li Signed-off-by: Jaegeuk Kim --- v6: - rebase the code Documentation/filesystems/f2fs.rst | 4 + fs/f2fs/checkpoint.c | 7 +- fs/f2fs/f2fs.h

Re: [f2fs-dev] [PATCH v6] f2fs: support in-memory inode checksum when checking consistency

On 07/15, Chao Yu wrote: > Hi Weichao and Jaegeuk, > > On 2018/6/22 15:16, Chao Yu wrote: > > On 2018/6/12 22:36, Chao Yu wrote: > >> Ping, > >> > >> Jaegeuk, sometimes, we suffer data corruption caused by bit-transition of > >> cache, > >> we troubleshoot for weeks or months, and finally, find

Re: [f2fs-dev] [PATCH v6] f2fs: support in-memory inode checksum when checking consistency

Hi Weichao and Jaegeuk, On 2018/6/22 15:16, Chao Yu wrote: > On 2018/6/12 22:36, Chao Yu wrote: >> Ping, >> >> Jaegeuk, sometimes, we suffer data corruption caused by bit-transition of >> cache, >> we troubleshoot for weeks or months, and finally, find that it is caused by >> hardware. So for

Re: [f2fs-dev] [PATCH v6] f2fs: support in-memory inode checksum when checking consistency

On 2018/6/12 22:36, Chao Yu wrote: > Ping, > > Jaegeuk, sometimes, we suffer data corruption caused by bit-transition of > cache, > we troubleshoot for weeks or months, and finally, find that it is caused by > hardware. So for this case, maybe in-memory checksum can help to troubleshoot > more

Re: [f2fs-dev] [PATCH v6] f2fs: support in-memory inode checksum when checking consistency

Ping, Jaegeuk, sometimes, we suffer data corruption caused by bit-transition of cache, we troubleshoot for weeks or months, and finally, find that it is caused by hardware. So for this case, maybe in-memory checksum can help to troubleshoot more quickly. Could you consider this? Thanks, On

Re: [f2fs-dev] [PATCH v6] f2fs: support in-memory inode checksum when checking consistency

On 2018/3/9 23:10, Weichao Guo wrote: > Enable in-memory inode checksum to protect metadata blocks from > in-memory scribbles when checking consistency, which has no > performance requirements. > > Signed-off-by: Weichao Guo Reviewed-by: Chao Yu

[f2fs-dev] [PATCH v6] f2fs: support in-memory inode checksum when checking consistency

Enable in-memory inode checksum to protect metadata blocks from in-memory scribbles when checking consistency, which has no performance requirements. Signed-off-by: Weichao Guo --- fs/f2fs/inode.c | 7 +++ fs/f2fs/node.c | 10 +- 2 files changed, 16

Re: [f2fs-dev] [PATCH v6] F2FS support

Hi Andrei, I'll send v7 which addresses your comment. Thanks, On Mon, Feb 22, 2016 at 12:25:26PM +0300, Andrei Borzenkov wrote: > 08.01.2016 22:41, Jaegeuk Kim пишет: > > Change log from v5: > > o fix build warning for ARM, reported by Michael Zimmermann > > > > Thanks to Michael for testing

Re: [f2fs-dev] [PATCH v6] F2FS support

08.01.2016 22:41, Jaegeuk Kim пишет: > Change log from v5: > o fix build warning for ARM, reported by Michael Zimmermann > > Thanks to Michael for testing this patch. > > -- >8 -- > From 284fd2a6d5e07770cc021c8f59b538471c35 Mon Sep 17 00:00:00 2001 > From: Jaegeuk Kim >

Re: [f2fs-dev] [PATCH v6] F2FS support

Change log from v5: o fix build warning for ARM, reported by Michael Zimmermann Thanks to Michael for testing this patch. -- >8 -- From 284fd2a6d5e07770cc021c8f59b538471c35 Mon Sep 17 00:00:00 2001 From: Jaegeuk Kim Date: Tue, 17 Nov 2015 12:45:13 -0800 Subject: [PATCH]