From: Steven Rostedt <rostedt@goodmis.org>
To: Ajay Kaher <akaher@vmware.com>
Cc: shuah@kernel.org, mhiramat@kernel.org, chinglinyu@google.com,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, lkp@intel.com,
namit@vmware.com, oe-lkp@lists.linux.dev, amakhalov@vmware.com,
er.ajay.kaher@gmail.com, srivatsa@csail.mit.edu,
tkundu@vmware.com, vsirnapalli@vmware.com
Subject: Re: [PATCH v5 06/10] eventfs: Implement eventfs lookup, read, open functions
Date: Wed, 26 Jul 2023 16:28:20 -0400 [thread overview]
Message-ID: <20230726162820.28e3a492@rorschach.local.home> (raw)
In-Reply-To: <1690054625-31939-7-git-send-email-akaher@vmware.com>
On Sun, 23 Jul 2023 01:07:01 +0530
Ajay Kaher <akaher@vmware.com> wrote:
> Add the inode_operations, file_operations, and helper functions to eventfs:
> dcache_dir_open_wrapper()
> eventfs_root_lookup()
> eventfs_release()
> eventfs_set_ef_status_free()
> eventfs_post_create_dir()
>
> The inode_operations and file_operations functions will be called from the
> VFS layer.
>
I would add in this change log:
create_file() and create_dir() are added as stub functions and will
be filled in later.
> Signed-off-by: Ajay Kaher <akaher@vmware.com>
> Co-developed-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
> Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
> Tested-by: Ching-lin Yu <chinglinyu@google.com>
> ---
> fs/tracefs/event_inode.c | 312 +++++++++++++++++++++++++++++++++++++++
> fs/tracefs/internal.h | 2 +
> 2 files changed, 314 insertions(+)
>
-- Steve
next prev parent reply other threads:[~2023-07-26 20:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-22 19:36 [PATCH v5 00/10] tracing: introducing eventfs Ajay Kaher
2023-07-22 19:36 ` [PATCH v5 01/10] tracing: Require all trace events to have a TRACE_SYSTEM Ajay Kaher
2023-07-22 19:36 ` [PATCH v5 02/10] eventfs: Implement tracefs_inode_cache Ajay Kaher
2023-07-25 23:06 ` Steven Rostedt
2023-07-26 18:45 ` Ajay Kaher
2023-07-26 21:39 ` Steven Rostedt
2023-07-22 19:36 ` [PATCH v5 03/10] tracefs: Rename and export some tracefs functions Ajay Kaher
2023-07-22 19:36 ` [PATCH v5 04/10] eventfs: Implement eventfs dir creation functions Ajay Kaher
2023-07-22 19:37 ` [PATCH v5 05/10] eventfs: Implement eventfs file add functions Ajay Kaher
2023-07-22 19:37 ` [PATCH v5 06/10] eventfs: Implement eventfs lookup, read, open functions Ajay Kaher
2023-07-26 20:28 ` Steven Rostedt [this message]
2023-07-26 20:51 ` Steven Rostedt
2023-07-22 19:37 ` [PATCH v5 07/10] eventfs: Implement functions to create files and dirs when accessed Ajay Kaher
2023-07-26 20:34 ` Steven Rostedt
2023-07-22 19:37 ` [PATCH v5 08/10] eventfs: Implement removal of meta data from eventfs Ajay Kaher
2023-07-22 19:37 ` [PATCH v5 09/10] eventfs: Move tracing/events to eventfs Ajay Kaher
2023-07-22 19:37 ` [PATCH v5 10/10] test: ftrace: Fix kprobe test for eventfs Ajay Kaher
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=20230726162820.28e3a492@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=akaher@vmware.com \
--cc=amakhalov@vmware.com \
--cc=chinglinyu@google.com \
--cc=er.ajay.kaher@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mhiramat@kernel.org \
--cc=namit@vmware.com \
--cc=oe-lkp@lists.linux.dev \
--cc=shuah@kernel.org \
--cc=srivatsa@csail.mit.edu \
--cc=tkundu@vmware.com \
--cc=vsirnapalli@vmware.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