On Wed, May 30, 2018 at 05:12:16PM +0200, Miklos Szeredi wrote:
> >> From: Vivek Goyal
> >>
> >> ovl_open() should open file which contains data and not open metacopy
> >> inode. With the introduction of metacopy inodes, with current
> >> implementaion we will end up opening metacopy inode as wel
On Wed, May 30, 2018 at 4:30 PM, Vivek Goyal wrote:
> On Tue, May 29, 2018 at 04:45:59PM +0200, Miklos Szeredi wrote:
>> From: Vivek Goyal
>>
>> ovl_open() should open file which contains data and not open metacopy
>> inode. With the introduction of metacopy inodes, with current
>> implementaion
On Tue, May 29, 2018 at 04:45:59PM +0200, Miklos Szeredi wrote:
> From: Vivek Goyal
>
> ovl_open() should open file which contains data and not open metacopy
> inode. With the introduction of metacopy inodes, with current
> implementaion we will end up opening metacopy inode as well.
>
> But th
From: Vivek Goyal
ovl_open() should open file which contains data and not open metacopy
inode. With the introduction of metacopy inodes, with current
implementaion we will end up opening metacopy inode as well.
But there can be certain circumstances like ovl_fsync() where we want to
allow openi
4 matches
Mail list logo