and the commit exists at https://src.openvz.org/projects/OVZ/repos/vzkernel/browse/fs/ext4/namei.c?at=refs%2Fheads%2Fbranch-rh7-3.10.0-327.28.2.vz7.17.x-ovz . Could it be lost?
On Mon, Oct 17, 2016 at 11:48 AM, Vladimir Meshkov <vmesh...@cloudlinux.com> wrote: > Could you please clarify why we cannot find the commit at > https://src.openvz.org/projects/OVZ/repos/vzkernel/ > browse/fs/ext4/namei.c?at=refs/heads/branch-rh7-3.10.0- > 327.36.1.vz7.18.x-ovz ? Thank you. > > On Fri, Oct 14, 2016 at 9:23 PM, Maxim Patlasov <mpatla...@virtuozzo.com> > wrote: > >> Thanks! You may be interested to search devel@openvz.org archives for: >> >> Subject: [PATCH rh7] ext4: ext4_mkdir must set S_IOPS_WRAPPER bit >> >> Date: Mon, 25 Jul 2016 14:01:16 -0700 >> >> On 10/14/2016 09:47 AM, Vladimir Meshkov wrote: >> >> ext4 supports an extended operations like rename2, but >> inode isn't correctly marked after mkdir. >> >> Signed-off-by: Alexey Lyashkov <u...@cloudlinux.com >> <https://e.mail.ru/compose?To=u...@cloudlinux.com>> >> --- >> fs/ext4/namei.c | 1 + >> 1 file changed, 1 insertion(+) >> >> diff --git a/fs/ext4/namei.c b/fs/ext4/namei.c >> index 0adc6df..bebe698 100644 >> --- a/fs/ext4/namei.c >> +++ b/fs/ext4/namei.c >> @@ -2413,6 +2413,7 @@ retry: >> >> inode->i_op = &ext4_dir_inode_operations.ops; >> inode->i_fop = &ext4_dir_operations; >> + inode->i_flags |= S_IOPS_WRAPPER; >> err = ext4_init_new_dir(handle, dir, inode); >> if (err) >> goto out_clear_inode; >> -- >> 1.8.3.1 >> >> >> _______________________________________________ >> Devel mailing >> listDevel@openvz.orghttps://lists.openvz.org/mailman/listinfo/devel >> >> >> >
_______________________________________________ Devel mailing list Devel@openvz.org https://lists.openvz.org/mailman/listinfo/devel
