From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Wu Bo <wubo.oduw@gmail.com>
Cc: linux-kernel@vger.kernel.org, Wu Bo <bo.wu@vivo.com>,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/1] f2fs: pass I_NEW flag to trace event
Date: Wed, 17 May 2023 17:32:57 -0700 [thread overview]
Message-ID: <ZGVyOTqQy5ZhNvAr@google.com> (raw)
In-Reply-To: <4a512db8-cfca-80a5-ba62-780f56d014f6@gmail.com>
On 05/17, Wu Bo wrote:
> On 2023/5/17 16:36, Chao Yu wrote:
> > On 2023/5/17 11:59, Wu Bo wrote:
> > > On 2023/5/17 10:44, Chao Yu wrote:
> > > > On 2023/5/16 20:07, Wu Bo wrote:
> > > > > Modify the order between 'trace_f2fs_iget' &
> > > > > 'unlock_new_inode', so the
> > > > > I_NEW can pass to the trace event when the inode initialised.
> > > >
> > > > Why is it needed? And trace_f2fs_iget() won't print inode->i_state?
> > >
> > > When connect a trace_probe to f2fs_iget, it will be able to
> > > determine whether
> > > the inode is new initialised in order to do different process.
> >
> > I didn't get it, you want to hook __tracepoint_f2fs_iget() w/ your own
> > callback?
> Yes, to use 'tracepoint_probe_register ' to register a probe at
> trace_f2fs_iget
Why?
> >
> > Thanks,
> >
> > >
> > > >
> > > > Thanks,
> > > >
> > > > >
> > > > > Signed-off-by: Wu Bo <bo.wu@vivo.com>
> > > > > ---
> > > > > fs/f2fs/inode.c | 2 +-
> > > > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > > > >
> > > > > diff --git a/fs/f2fs/inode.c b/fs/f2fs/inode.c
> > > > > index cf4327ad106c..caf959289fe7 100644
> > > > > --- a/fs/f2fs/inode.c
> > > > > +++ b/fs/f2fs/inode.c
> > > > > @@ -577,8 +577,8 @@ struct inode *f2fs_iget(struct super_block *sb,
> > > > > unsigned long ino)
> > > > > file_dont_truncate(inode);
> > > > > }
> > > > > - unlock_new_inode(inode);
> > > > > trace_f2fs_iget(inode);
> > > > > + unlock_new_inode(inode);
> > > > > return inode;
> > > > > bad_inode:
> > > >
> > > >
> > > > _______________________________________________
> > > > Linux-f2fs-devel mailing list
> > > > Linux-f2fs-devel@lists.sourceforge.net
> > > > https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
> > > >
_______________________________________________
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:[~2023-05-18 0:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 12:07 [f2fs-dev] [PATCH 1/1] f2fs: pass I_NEW flag to trace event Wu Bo via Linux-f2fs-devel
2023-05-17 2:44 ` Chao Yu
2023-05-17 3:59 ` Wu Bo via Linux-f2fs-devel
2023-05-17 8:36 ` Chao Yu
2023-05-17 14:31 ` Wu Bo
2023-05-18 0:32 ` Jaegeuk Kim [this message]
2023-05-18 15:02 ` Wu Bo
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=ZGVyOTqQy5ZhNvAr@google.com \
--to=jaegeuk@kernel.org \
--cc=bo.wu@vivo.com \
--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).