Messages in this thread | | | Date | Fri, 21 Jun 2013 16:30:16 +0900 | Subject | Re: [f2fs-dev] [PATCH 1/4] f2fs: reorganize the f2fs_setattr() function. | From | Namjae Jeon <> |
| |
> > Sorry for late. I was very busy. > > Could you tell me if it happens difference between xattr and i_mode, > what will you do? First of all, I want to know which case make mismatching permission between xattr and i_mode. And when we call chmod, inode is locked in sys_chmod. If so, inode->i_mode can be changed by any updated inode during chmod although inode is locked ?
> The purpose of i_acl_mode is used to update i_mode and xattr together in > same lock region. Could you please tell me what is same lock region ? (inode->i_mutex or mutex_lock_op(sbi))
Thanks. > >> >> > >> > ---------------------------------------------------------------------------------------------------------------- >> > Subject: [PATCH v2] f2fs: reorganize the f2fs_setattr(), f2fs_set_acl, >> > f2fs_setxattr() >> > From: Namjae Jeon <namjae.jeon@samsung.com> >> >
| |