From: Sheng Yong <shengyong2021@gmail.com>
To: Chao Yu <chao@kernel.org>, jaegeuk@kernel.org
Cc: shengyong1@xiaomi.com, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [RFC PATCH v2 13/32] inject.f2fs: add member `filename' in inject_dentry
Date: Mon, 16 Jun 2025 10:01:28 +0800 [thread overview]
Message-ID: <7b8ee3f3-b572-4f91-8954-adde5b874089@gmail.com> (raw)
In-Reply-To: <92fa6c87-4780-47eb-986c-1bc19db085f1@kernel.org>
On 6/13/25 15:55, Chao Yu wrote:
> On 2025/6/10 20:37, Sheng Yong wrote:
>> From: Sheng Yong <shengyong1@xiaomi.com>
>>
>> This patch adds a new member `filename' in inject_dentry to inject
>> dentry filename. The dentry is specified by nid option.
>>
>> Note that '.' and '..' dentries are special, because they are not in the
>> parent directory of nid. So this patch also adds a new option `--dots'
>> to inject these two dentries.
>>
>> Signed-off-by: Sheng Yong <shengyong1@xiaomi.com>
>> ---
>> fsck/inject.c | 94 ++++++++++++++++++++++++++++++++++++++++-------
>> fsck/inject.h | 1 +
>> man/inject.f2fs.8 | 12 +++++-
>> 3 files changed, 92 insertions(+), 15 deletions(-)
>>
>> diff --git a/fsck/inject.c b/fsck/inject.c
>> index 8c2f8c5dc332..5eb913fefad7 100644
>> --- a/fsck/inject.c
>> +++ b/fsck/inject.c
[...]
>> @@ -1265,6 +1301,36 @@ static int inject_dentry(struct f2fs_sb_info *sbi, struct inject_option *opt)
>> "%d -> %d\n", opt->nid, dent->file_type,
>> (u8)opt->val);
>> dent->file_type = (u8)opt->val;
>> + } else if (!strcmp(opt->mb, "filename")) {
>> + if (!opt->str) {
>> + ERR_MSG("option str is needed\n");
>> + ret = -EINVAL;
>> + goto out;
>> + }
>> + namecap = ALIGN_UP(le16_to_cpu(dent->name_len), F2FS_SLOT_LEN);
>> + namelen = strlen(opt->str);
>> + if (namelen > namecap || namelen > F2FS_NAME_LEN) {
>> + ERR_MSG("option str too long\n");
>> + ret = -EINVAL;
>> + goto out;
>> + }
>> + name = (char *)d.filename[slot];
>> + MSG(0, "Info: inject dentry filename of nid %u: "
>> + "%.*s -> %s\n", opt->nid, le16_to_cpu(dent->name_len),
>> + name, opt->str);
>> + memcpy(name, opt->str, namelen);
>> + MSG(0, "Info: inject dentry namelen of nid %u: "
>> + "%d -> %d\n", opt->nid, le16_to_cpu(dent->name_len),
>> + namelen);
>> + dent->name_len = cpu_to_le16(namelen);
>> + dentry_hash = f2fs_dentry_hash(get_encoding(sbi),
>> + IS_CASEFOLDED(inode),
>> + (unsigned char *)name,
>> + namelen);
>> + MSG(0, "Info: inject dentry d_hash of nid %u: "
>> + "0x%x -> 0x%x\n", opt->nid, le32_to_cpu(dent->hash_code),
>> + dentry_hash);
>> + dent->hash_code = cpu_to_le32(dentry_hash);
>
> Yong,
>
> Out of curiosity, if we inject filename in target dirent, according new
> filename's hash, it may be located in dentry block which belongs to another
> bucket, can fsck repair it?
Hi, Chao,
Yes, I think fsck can repair it, but it removes the entry directly instead of
"reordering" it (`f2fs_check_dirent_position`). I can add a test for this case.
Thanks,
shengyong
>
> Thanks,
>
>> } else {
>> ERR_MSG("unknown or unsupported member \"%s\"\n", opt->mb);
>> ret = -EINVAL;
>> diff --git a/fsck/inject.h b/fsck/inject.h
>> index 43c21b56a7eb..706a211bc645 100644
>> --- a/fsck/inject.h
>> +++ b/fsck/inject.h
>> @@ -30,6 +30,7 @@ struct inject_option {
>> int cp; /* which cp */
>> int nat; /* which nat pack */
>> int sit; /* which sit pack */
>> + int dots; /* . or .. dentry */
>> bool ssa;
>> bool node;
>> bool dent;
>> diff --git a/man/inject.f2fs.8 b/man/inject.f2fs.8
>> index 72d1c90f7ce4..27b66f59b77d 100644
>> --- a/man/inject.f2fs.8
>> +++ b/man/inject.f2fs.8
>> @@ -214,7 +214,14 @@ inode i_nid array specified by \fIidx\fP.
>> .RE
>> .TP
>> .BI \-\-dent
>> -Inject dentry block or dir entry specified \fInid\fP.
>> +Inject dentry block or dir entry specified by \fInid\fP.
>> +.RS 1.2i
>> +.TP
>> +.BI \-\-dots " 1 or 2"
>> +The option means the "." or ".." directory entry of \fInid\fP is going to be injected.
>> +.RE
>> +.TP
>> +.BI ""
>> The available \fImb\fP of \fIdent\fP are:
>> .RS 1.2i
>> .TP
>> @@ -229,6 +236,9 @@ dentry ino.
>> .TP
>> .BI d_ftype
>> dentry ftype.
>> +.TP
>> +.BI filename
>> +dentry filename, and corresponding d_hash and namelen are updated implicitly.
>> .RE
>> .TP
>> .BI \-\-dry\-run
>
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2025-06-16 2:01 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 12:37 [f2fs-dev] [RFC PATCH v2 00/32] f2fs-tools: add testcases Sheng Yong
2025-06-10 12:37 ` [f2fs-dev] [RFC PATCH v2 01/32] fsck.f2fs: do not finish/reset zone if dry-run is true Sheng Yong
2025-06-10 12:37 ` [f2fs-dev] [RFC PATCH v2 02/32] f2fs-tools: add option N to answer no for all questions Sheng Yong
2025-06-11 9:22 ` Chao Yu via Linux-f2fs-devel
2025-06-11 9:36 ` Sheng Yong
2025-06-10 12:37 ` [f2fs-dev] [RFC PATCH v2 03/32] f2fs-tools: cleanup {nid|segno}_in_journal Sheng Yong
2025-06-10 12:37 ` [f2fs-dev] [RFC PATCH v2 04/32] fsck.f2fs: fix invalidate checkpoint Sheng Yong
2025-06-10 12:37 ` [f2fs-dev] [RFC PATCH v2 05/32] dump.f2fs: print more info Sheng Yong
2025-06-10 12:37 ` [f2fs-dev] [RFC PATCH v2 06/32] f2fs-tools: add and export lookup_sit_in_journal Sheng Yong
2025-06-10 12:37 ` [f2fs-dev] [RFC PATCH v2 07/32] inject.f2fs: fix injecting sit/nat in journal Sheng Yong
2025-06-11 11:42 ` Chao Yu via Linux-f2fs-devel
2025-06-10 12:37 ` [f2fs-dev] [RFC PATCH v2 08/32] inject.f2fs: fix injection on zoned device Sheng Yong
2025-06-10 12:37 ` [f2fs-dev] [RFC PATCH v2 09/32] inject.f2fs: fix and cleanup parsing numeric options Sheng Yong
2025-06-13 6:08 ` Chao Yu via Linux-f2fs-devel
2025-06-16 1:49 ` Sheng Yong
2025-06-10 12:37 ` [f2fs-dev] [RFC PATCH v2 10/32] inject.f2fs: add members in inject_cp Sheng Yong
2025-06-13 7:30 ` Chao Yu via Linux-f2fs-devel
2025-06-10 12:37 ` [f2fs-dev] [RFC PATCH v2 11/32] inject.f2fs: add member `feature' in inject_sb Sheng Yong
2025-06-10 12:37 ` [f2fs-dev] [RFC PATCH v2 12/32] inject.f2fs: add members in inject_node Sheng Yong
2025-06-13 7:38 ` Chao Yu via Linux-f2fs-devel
2025-06-10 12:37 ` [f2fs-dev] [RFC PATCH v2 13/32] inject.f2fs: add member `filename' in inject_dentry Sheng Yong
2025-06-13 7:55 ` Chao Yu via Linux-f2fs-devel
2025-06-16 2:01 ` Sheng Yong [this message]
2025-06-10 12:37 ` [f2fs-dev] [RFC PATCH v2 14/32] tests: prepare helper scripts for testcases Sheng Yong
2025-06-10 12:37 ` [f2fs-dev] [RFC PATCH v2 15/32] tests: add fsck testcase of fixing bad super magic Sheng Yong
2025-06-10 12:37 ` [f2fs-dev] [RFC PATCH v2 16/32] tests: add fsck testcase of fixing errors recorded in sb Sheng Yong
2025-06-10 12:37 ` [f2fs-dev] [RFC PATCH v2 17/32] tests: add fsck testcase of fixing cp crc Sheng Yong
2025-06-10 12:37 ` [f2fs-dev] [RFC PATCH v2 18/32] tests: add fsck testcase of fixing nat entry with invalid ino Sheng Yong
2025-06-10 12:37 ` [f2fs-dev] [RFC PATCH v2 19/32] tests: add fsck testcase of fixing nat entry with invalid blkaddr Sheng Yong
2025-06-10 12:37 ` [f2fs-dev] [RFC PATCH v2 20/32] tests: add fsck testcase of fixing sit entry type Sheng Yong
2025-06-10 12:37 ` [f2fs-dev] [RFC PATCH v2 21/32] tests: add fsck testcase of fixing sit entry vblocks Sheng Yong
2025-06-10 12:37 ` [f2fs-dev] [RFC PATCH v2 22/32] tests: add fsck testcase of fixing sit entry valid_map Sheng Yong
2025-06-10 12:37 ` [f2fs-dev] [RFC PATCH v2 23/32] tests: add fsck testcase of fixing sum entry nid Sheng Yong
2025-06-10 12:37 ` [f2fs-dev] [RFC PATCH v2 24/32] tests: add fsck testcase of fixing sum footer type Sheng Yong
2025-06-10 12:37 ` [f2fs-dev] [RFC PATCH v2 25/32] tests: add fsck testcase of fixing sum entry ofs_in_node Sheng Yong
2025-06-10 12:37 ` [f2fs-dev] [RFC PATCH v2 26/32] tests: add fsck testcase of fixing inode invalid i_addr Sheng Yong
2025-06-10 12:37 ` [f2fs-dev] [RFC PATCH v2 27/32] tests: add fsck testcase of fixing dentry hash code Sheng Yong
2025-06-10 12:37 ` [f2fs-dev] [RFC PATCH v2 28/32] tests: add fsck testcase of fixing lost dots Sheng Yong
2025-06-10 12:37 ` [f2fs-dev] [RFC PATCH v2 29/32] tests: add fsck testcase of fixing duplicated dots Sheng Yong
2025-06-10 12:37 ` [f2fs-dev] [RFC PATCH v2 30/32] tests: add fsck testcase of fixing loop fsync dnodes Sheng Yong
2025-06-10 12:37 ` [f2fs-dev] [RFC PATCH v2 31/32] tests: add inject testcase of injecting META area Sheng Yong
2025-06-10 12:37 ` [f2fs-dev] [RFC PATCH v2 32/32] tests: add inject testcase of injecting node block Sheng Yong
2025-08-15 10:38 ` [f2fs-dev] [RFC PATCH v2 00/32] f2fs-tools: add testcases Chao Yu via Linux-f2fs-devel
2025-08-15 11:27 ` Sheng Yong
2025-08-16 7:04 ` Chao Yu via Linux-f2fs-devel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7b8ee3f3-b572-4f91-8954-adde5b874089@gmail.com \
--to=shengyong2021@gmail.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=shengyong1@xiaomi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.