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

2013-12-22 Thread Jaegeuk Kim
Hi, I couldn't get any error when replaying your scenario on my arm board. So, could you send the backtrace of any hanged process? # cat /proc/[pid]/stack Thanks, 2013-12-20 (금), 12:29 -0800, John Grub: Hello, I can't seem to write larger files on my f2fs mount. My hardware is an embedded

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

2013-12-22 Thread Jaegeuk Kim
2013-12-21 (토), 18:01 +0800, Chao Yu: 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.

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

2013-12-22 Thread Chao Yu
Hi Kim, -Original Message- From: Jaegeuk Kim [mailto:jaegeuk@samsung.com] Sent: Monday, December 23, 2013 9:26 AM To: Chao Yu Cc: linux-fsde...@vger.kernel.org; linux-ker...@vger.kernel.org; linux-f2fs-devel@lists.sourceforge.net Subject: Re: [f2fs-dev] [PATCH 1/3] f2fs: check

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

2013-12-22 Thread Chao Yu
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