Re: [f2fs-dev] [bug] writes hanging

Nothing in the kernel log. Disabling discard when formatting the partition doesn't help. On Dec 21, 2013 1:06 PM, "Chris Fries" wrote: > Anything show up in the kernel log from the block device? You might try > turning off discard, see if that helps. > On Dec 21, 2013 2:16 PM, "John Grub" wrote

Re: [f2fs-dev] [bug] writes hanging

Anything show up in the kernel log from the block device? You might try turning off discard, see if that helps. On Dec 21, 2013 2:16 PM, "John Grub" wrote: > Note: this is on a M8G2FA Samsung flash chip. > > > On Fri, Dec 20, 2013 at 12:29 PM, John Grub wrote: > >> Hello, >> >> I can't seem to

Re: [f2fs-dev] [bug] writes hanging

Note: this is on a M8G2FA Samsung flash chip. On Fri, Dec 20, 2013 at 12:29 PM, John Grub wrote: > Hello, > > I can't seem to write larger files on my f2fs mount. > My hardware is an embedded arm platform with an 8GB eMMC nand flash chip: > Golbalscale > D2Plug

[f2fs-dev] [PATCH 3/3] f2fs: avoid to set wrong pino of inode when rename dir

When we rename a dir to new name which is not exist previous, we will set pino of parent inode with ino of child inode in f2fs_set_link. It destroy consistency of pino, it should be fixed. Thanks for previous work of Shu Tan. Signed-off-by: Shu Tan Signed-off-by: Chao Yu --- fs/f2fs/dir.c |

[f2fs-dev] [PATCH 1/3] f2fs: check filename length in recover_dentry

In current flow, we will get Null return value of f2fs_find_entry in recover_dentry when name.len is bigger than F2FS_NAME_LEN, and then we still add this inode into its dir entry. To avoid this situation, we must check filename length before we use it. Another point is that we could remove the co

[f2fs-dev] [PATCH 2/3] f2fs: update several comments

Update several comments: 1. use f2fs_{un}lock_op install of mutex_{un}lock_op. 2. update comment of get_data_block(). 3. update description of node offset. Signed-off-by: Chao Yu --- fs/f2fs/data.c | 14 -- fs/f2fs/dir.c |4 ++-- fs/f2fs/f2fs.h |2 +- fs/f2fs/node.c |8