From: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>, Wu Bo <bo.wu@vivo.com>
Cc: wubo.oduw@gmail.com, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2 1/1] f2fs: fix args passed to trace_f2fs_lookup_end
Date: Wed, 31 May 2023 09:11:54 +0800 [thread overview]
Message-ID: <9f2948cb-a4b0-bced-1d11-cf9fc712ba9b@kernel.org> (raw)
In-Reply-To: <ZHaHknKmSQIdQzBC@google.com>
On 2023/5/31 7:32, Jaegeuk Kim wrote:
> On 05/30, Wu Bo wrote:
>> The NULL return of 'd_splice_alias' dosen't mean error. Thus the
>> successful case will also return NULL, which makes the tracepoint always
>> print 'err=-ENOENT'.
>>
>> Signed-off-by: Wu Bo <bo.wu@vivo.com>
>> ---
>> fs/f2fs/namei.c | 5 +++--
>> 1 file changed, 3 insertions(+), 2 deletions(-)
>>
>> diff --git a/fs/f2fs/namei.c b/fs/f2fs/namei.c
>> index 77a71276ecb1..0c5e4c424eab 100644
>> --- a/fs/f2fs/namei.c
>> +++ b/fs/f2fs/namei.c
>> @@ -576,8 +576,9 @@ static struct dentry *f2fs_lookup(struct inode *dir, struct dentry *dentry,
>> }
>> #endif
>> new = d_splice_alias(inode, dentry);
>> - err = PTR_ERR_OR_ZERO(new);
>> - trace_f2fs_lookup_end(dir, dentry, ino, !new ? -ENOENT : err);
>> + if (IS_ERR(new))
>> + err = PTR_ERR(new);
>> + trace_f2fs_lookup_end(dir, new ? new : dentry, ino, err);
>
> Again, new can be an error pointer, and the previous err was supposed to be
> zero or -ENOENT.
>
> case 1) dentry exists: err (0) with new (NULL) --> dentry, err=0
> case 2) dentry exists: err (0) with new (VALID) --> new, err=0
> case 3) dentry exists: err (0) with new (ERR) --> dentry, err=ERR
> case 4) no dentry exists: err (-ENOENT) with new (NULL) --> dentry, err=-ENOENT
> case 4) no dentry exists: err (-ENOENT) with new (VALID) --> new, err=-ENOENT
> case 5) no dentry exists: err (-ENOENT) with new (ERR) --> dentry, err=ERR
>
> trace_f2fs_lookup_end(dir, !IS_ERR_OR_NULL(new) ? new : dentry,
> ino, IS_ERR(new) ? PTR_ERR(new) : err);
Agreed, could you please add above description in commit message?
Thanks,
>
>
>> return new;
>> out_iput:
>> iput(inode);
>> --
>> 2.35.3
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2023-05-31 1:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 1:21 [f2fs-dev] [PATCH v2 1/1] f2fs: fix args passed to trace_f2fs_lookup_end Wu Bo via Linux-f2fs-devel
2023-05-30 1:51 ` Chao Yu
2023-05-30 23:32 ` Jaegeuk Kim
2023-05-31 1:11 ` Chao Yu [this message]
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=9f2948cb-a4b0-bced-1d11-cf9fc712ba9b@kernel.org \
--to=chao@kernel.org \
--cc=bo.wu@vivo.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=wubo.oduw@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).