In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()...if (old_dir != new_dir && !whiteout)f2fs_set_link(old_inode, old_dir_entry,old_dir_page, new_dir);elsef2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()...if (old_dir != new_dir && !whiteout)f2fs_set_link(old_inode, old_dir_entry,old_dir_page, new_dir);elsef2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you dbeen askedto leave awhiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. ,parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()...if (old_dir != new_dir && !whiteout)f2fs_set_link(old_inode, old_dir_entry,old_dir_page, new_dir);elsef2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if youd been askedto leavea whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .., parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()...if (old_dir != new_dir && !whiteout)f2fs_set_link(old_inode, old_dir_entry,old_dir_page, new_dir);elsef2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you dbeen askedto leave awhiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. ,parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()...if (old_dir != new_dir && !whiteout)f2fs_set_link(old_inode, old_dir_entry,old_dir_page, new_dir);elsef2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if youd been askedto leavea whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .., parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()...if (old_dir != new_dir && !whiteout)f2fs_set_link(old_inode, old_dir_entry,old_dir_page, new_dir);elsef2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you dbeen askedto leave awhiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. ,parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()...if (old_dir != new_dir && !whiteout)f2fs_set_link(old_inode, old_dir_entry,old_dir_page, new_dir);elsef2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if youd been askedto leavea whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .., parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()...if (old_dir != new_dir && !whiteout)f2fs_set_link(old_inode, old_dir_entry,old_dir_page, new_dir);elsef2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you dbeen askedto leave awhiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. ,parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()...if (old_dir != new_dir && !whiteout)f2fs_set_link(old_inode, old_dir_entry,old_dir_page, new_dir);elsef2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if youd been askedto leavea whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .., parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()...if (old_dir != new_dir && !whiteout)f2fs_set_link(old_inode, old_dir_entry,old_dir_page, new_dir);elsef2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you dbeen askedto leave awhiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. ,parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()...if (old_dir != new_dir && !whiteout)f2fs_set_link(old_inode, old_dir_entry,old_dir_page, new_dir);elsef2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if youd been askedto leavea whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .., parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
Inthe Linux kernel, thefollowing vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()...if (old_dir != new_dir && !whiteout)f2fs_set_link(old_inode, old_dir_entry,old_dir_page, new_dir);elsef2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move thesource to new parent, even if you d been askedto leave a whiteout in the oldplace.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With belowtestcase, itmay cause dirent corruption,due to it missedto call f2fs_set_link()to update .. link to new directory.- mkdir -p dir/foo-renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) -->Bad inode number[0x4]for .. , parent parent ino is [0x3][FSCK] othercorruptedbugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
IntheLinuxkernel, the followingvulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()...if (old_dir != new_dir && !whiteout)f2fs_set_link(old_inode, old_dir_entry,old_dir_page, new_dir);elsef2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source tonew parent, even if you d been askedto leave a whiteout in the old place.[1]https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase,it may causedirent corruption, due to itmissedto call f2fs_set_link() to update .. linkto new directory.- mkdir -p dir/foo- renameat2-w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inodenumber[0x4] for .. ,parent parent ino is [0x3][FSCK] other corruptedbugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()...if (old_dir != new_dir && !whiteout)f2fs_set_link(old_inode, old_dir_entry,old_dir_page, new_dir);elsef2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you dbeen askedto leave awhiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. ,parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()...if (old_dir != new_dir && !whiteout)f2fs_set_link(old_inode, old_dir_entry,old_dir_page, new_dir);elsef2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if youd been askedto leavea whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .., parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()...if (old_dir != new_dir && !whiteout)f2fs_set_link(old_inode, old_dir_entry,old_dir_page, new_dir);elsef2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you dbeen askedto leave awhiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. ,parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()...if (old_dir != new_dir && !whiteout)f2fs_set_link(old_inode, old_dir_entry,old_dir_page, new_dir);elsef2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if youd been askedto leavea whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .., parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()...if (old_dir != new_dir && !whiteout)f2fs_set_link(old_inode, old_dir_entry,old_dir_page, new_dir);elsef2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you dbeen askedto leave awhiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. ,parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()...if (old_dir != new_dir && !whiteout)f2fs_set_link(old_inode, old_dir_entry,old_dir_page, new_dir);elsef2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if youd been askedto leavea whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .., parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()...if (old_dir != new_dir && !whiteout)f2fs_set_link(old_inode, old_dir_entry,old_dir_page, new_dir);elsef2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you dbeen askedto leave awhiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. ,parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()...if (old_dir != new_dir && !whiteout)f2fs_set_link(old_inode, old_dir_entry,old_dir_page, new_dir);elsef2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if youd been askedto leavea whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .., parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()...if (old_dir != new_dir && !whiteout)f2fs_set_link(old_inode, old_dir_entry,old_dir_page, new_dir);elsef2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you dbeen askedto leave awhiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. ,parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()...if (old_dir != new_dir && !whiteout)f2fs_set_link(old_inode, old_dir_entry,old_dir_page, new_dir);elsef2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if youd been askedto leavea whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .., parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()...if (old_dir != new_dir && !whiteout)f2fs_set_link(old_inode, old_dir_entry,old_dir_page, new_dir);elsef2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you dbeen askedto leave awhiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. ,parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()...if (old_dir != new_dir && !whiteout)f2fs_set_link(old_inode, old_dir_entry,old_dir_page, new_dir);elsef2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if youd been askedto leavea whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .., parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()...if (old_dir != new_dir && !whiteout)f2fs_set_link(old_inode, old_dir_entry,old_dir_page, new_dir);elsef2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you dbeen askedto leave awhiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. ,parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()...if (old_dir != new_dir && !whiteout)f2fs_set_link(old_inode, old_dir_entry,old_dir_page, new_dir);elsef2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if youd been askedto leavea whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .., parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()...if (old_dir != new_dir && !whiteout)f2fs_set_link(old_inode, old_dir_entry,old_dir_page, new_dir);elsef2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you dbeen askedto leave awhiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. ,parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()...if (old_dir != new_dir && !whiteout)f2fs_set_link(old_inode, old_dir_entry,old_dir_page, new_dir);elsef2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if youd been askedto leavea whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .., parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()...if (old_dir != new_dir && !whiteout)f2fs_set_link(old_inode, old_dir_entry,old_dir_page, new_dir);elsef2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you dbeen askedto leave awhiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. ,parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()...if (old_dir != new_dir && !whiteout)f2fs_set_link(old_inode, old_dir_entry,old_dir_page, new_dir);elsef2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if youd been askedto leavea whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .., parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()...if (old_dir != new_dir && !whiteout)f2fs_set_link(old_inode, old_dir_entry,old_dir_page, new_dir);elsef2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you dbeen askedto leave awhiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. ,parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()...if (old_dir != new_dir && !whiteout)f2fs_set_link(old_inode, old_dir_entry,old_dir_page, new_dir);elsef2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if youd been askedto leavea whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .., parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()...if (old_dir != new_dir && !whiteout)f2fs_set_link(old_inode, old_dir_entry,old_dir_page, new_dir);elsef2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you dbeen askedto leave awhiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. ,parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()...if (old_dir != new_dir && !whiteout)f2fs_set_link(old_inode, old_dir_entry,old_dir_page, new_dir);elsef2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if youd been askedto leavea whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .., parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()...if (old_dir != new_dir && !whiteout)f2fs_set_link(old_inode, old_dir_entry,old_dir_page, new_dir);elsef2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you dbeen askedto leave awhiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. ,parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()...if (old_dir != new_dir && !whiteout)f2fs_set_link(old_inode, old_dir_entry,old_dir_page, new_dir);elsef2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if youd been askedto leavea whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .., parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()...if (old_dir != new_dir && !whiteout)f2fs_set_link(old_inode, old_dir_entry,old_dir_page, new_dir);elsef2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you dbeen askedto leave awhiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. ,parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()...if (old_dir != new_dir && !whiteout)f2fs_set_link(old_inode, old_dir_entry,old_dir_page, new_dir);elsef2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if youd been askedto leavea whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .., parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()...if (old_dir != new_dir && !whiteout)f2fs_set_link(old_inode, old_dir_entry,old_dir_page, new_dir);elsef2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to avoid dirent corruptionAs Al reported in link[1]:f2fs_rename()... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0);You want correct inumber in the .. link. And cross-directoryrename does move the source to new parent, even if you d been askedto leave a whiteout in the old place.[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/With below testcase, it may cause dirent corruption, due to it missedto call f2fs_set_link() to update .. link to new directory.- mkdir -p dir/foo- renameat2 -w dir/foo bar[ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for .. , parent parent ino is [0x3][FSCK] other corrupted bugs [Fail]
