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

2017-05-04 Thread Adam Borowski
On Thu, May 04, 2017 at 11:12:40AM -0700, Jaegeuk Kim wrote: > "F2FS (Flash-Friendly File System) is flash-friendly file system which was > merged > into Linux kernel v3.8 in 2013. > > The motive for F2FS was to build a file system that from the start, takes into > account the characteristics of

[f2fs-dev] [PATCH] F2FS support

2017-05-04 Thread Jaegeuk Kim
"F2FS (Flash-Friendly File System) is flash-friendly file system which was merged into Linux kernel v3.8 in 2013. The motive for F2FS was to build a file system that from the start, takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC,

Re: [f2fs-dev] [PATCH 1/3] f2fs:dax: fix races between page faults and fallocate

2017-05-04 Thread Jaegeuk Kim
Hi Qiuyang, When I checked i_mmap_sem in ext4, do we also check it in: f2fs_vm_page_mkwrite filemap_fault f2fs_setattr f2fs_add_inline_entries It needs to think about how to reduce lock coverage below as well. Thanks, On 05/04, sunqiuyang wrote: > Currently in F2FS, page faults and falloca

Re: [f2fs-dev] [PATCH] attr: adbjust acl_max of f2fs

2017-05-04 Thread Jaegeuk Kim
On 05/04, Chao Yu wrote: > Hi Jaegeuk, > > On 2017/5/4 1:02, Jaegeuk Kim wrote: > > Hello, > > > > On 04/28, Chao Yu wrote: > >> From: Chao Yu > >> > >> f2fs has set inline_xattr as a default option, and introduced a new option > >> named 'noinline_xattr' for disabling default inline_xattr optio

Re: [f2fs-dev] [PATCH] attr: adbjust acl_max of f2fs

2017-05-04 Thread Chao Yu
Hi Jaegeuk, On 2017/5/4 1:02, Jaegeuk Kim wrote: > Hello, > > On 04/28, Chao Yu wrote: >> From: Chao Yu >> >> f2fs has set inline_xattr as a default option, and introduced a new option >> named 'noinline_xattr' for disabling default inline_xattr option. So in >> _acl_get_max we need to check 'no

Re: [f2fs-dev] [PATCH] fscrypt: correct collision claim for digested names

2017-05-04 Thread Theodore Ts'o
On Mon, May 01, 2017 at 11:43:32AM -0700, Eric Biggers wrote: > From: Eric Biggers > > As I noted on the mailing list, it's easier than I originally thought to > create intentional collisions in the digested names. Unfortunately it's > not too easy to solve this, so for now just fix the comment

Re: [f2fs-dev] [PATCH 3/7] f2fs: Make flush bios explicitely sync

2017-05-04 Thread Jan Kara
On Thu 04-05-17 09:32:11, Jan Kara wrote: > On Wed 03-05-17 14:22:46, Jaegeuk Kim wrote: > > Hi Jan, > > > > On 05/02, Jan Kara wrote: > > > Commit b685d3d65ac7 "block: treat REQ_FUA and REQ_PREFLUSH as > > > synchronous" removed REQ_SYNC flag from WRITE_{FUA|PREFLUSH|...} > > > definitions. gene

Re: [f2fs-dev] [PATCH 3/7] f2fs: Make flush bios explicitely sync

2017-05-04 Thread Jaegeuk Kim
On 05/04, Jan Kara wrote: > On Thu 04-05-17 09:32:11, Jan Kara wrote: > > On Wed 03-05-17 14:22:46, Jaegeuk Kim wrote: > > > Hi Jan, > > > > > > On 05/02, Jan Kara wrote: > > > > Commit b685d3d65ac7 "block: treat REQ_FUA and REQ_PREFLUSH as > > > > synchronous" removed REQ_SYNC flag from WRITE_{FU

Re: [f2fs-dev] [PATCH 3/7] f2fs: Make flush bios explicitely sync

2017-05-04 Thread Jan Kara
On Wed 03-05-17 14:22:46, Jaegeuk Kim wrote: > Hi Jan, > > On 05/02, Jan Kara wrote: > > Commit b685d3d65ac7 "block: treat REQ_FUA and REQ_PREFLUSH as > > synchronous" removed REQ_SYNC flag from WRITE_{FUA|PREFLUSH|...} > > definitions. generic_make_request_checks() however strips REQ_FUA and > >