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

2013-09-24 Thread 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 called internally from within F2FS and should > not call functions that are used by VFS handlers.

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

2013-09-24 Thread Russ Knize
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_metad

Re: [f2fs-dev] [PATCH] f2fs: optimize fs_lock for better performance

2013-09-11 Thread Russ Knize
it doesn't matter > with stress-testing. > Actually what I've concerned is that we should not grab two or > more fs_locks in the same call path. > Thanks, > > 2013/9/11 Russ Knize : >> Hi Jaegeuk/Gu, >> >> I've removed the lock and have been stress-tes