Re: [f2fs-dev] [RFC 1/1] f2fs: don't GC or take an fs_lock from f2fs_initxattrs()

Hi Russ, That's what I wanted before. Merged. Thanks, 2013-09-24 (화), 15:53 -0500, Russ Knize: > This is an alternate solution to the deadlock problem I mentioned in > my previous patch. > > On Tue, Sep 24, 2013 at 3:49 PM, Russ Knize wrote: > > From: Russ Knize > > > > f2fs_initxattrs() is ca

Re: [f2fs-dev] [RFC 1/1] f2fs: don't GC or take an fs_lock from f2fs_initxattrs()

On 09/25/2013 04:49 AM, Russ Knize wrote: > From: Russ Knize > > f2fs_initxattrs() is called internally from within F2FS and should > not call functions that are used by VFS handlers. This avoids > certain deadlocks: > > - vfs_create() > - f2fs_create() <-- takes an fs_lock > - f2fs_add_lin

Re: [f2fs-dev] [RFC 1/1] f2fs: don't GC or take an fs_lock from f2fs_initxattrs()

This is an alternate solution to the deadlock problem I mentioned in my previous patch. On Tue, Sep 24, 2013 at 3:49 PM, Russ Knize wrote: > From: Russ Knize > > f2fs_initxattrs() is called internally from within F2FS and should > not call functions that are used by VFS handlers. This avoids >

[f2fs-dev] [RFC 1/1] f2fs: don't GC or take an fs_lock from f2fs_initxattrs()

From: Russ Knize f2fs_initxattrs() is called internally from within F2FS and should not call functions that are used by VFS handlers. This avoids certain deadlocks: - vfs_create() - f2fs_create() <-- takes an fs_lock - f2fs_add_link() - __f2fs_add_link() - init_inode_metadata() -