From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH v4 0/3] eventfs: Fixing dynamic creation
Date: Tue, 31 Oct 2023 15:31:09 -0400 [thread overview]
Message-ID: <20231031193109.018322397@goodmis.org> (raw)
This is really just putting together two eventfs patches that were
stepping on each other in conflicts. I decided to rip out the free_ei()
part into its own patch (as that was what was confliciting.
This series is just a combination of:
https://lore.kernel.org/linux-trace-kernel/20231031111325.50087cd8@gandalf.local.home/
and
https://lore.kernel.org/linux-trace-kernel/20231031113627.2edfa83f@gandalf.local.home/
With the stripped out free_ei() patch.
Steven Rostedt (Google) (3):
eventfs: Have a free_ei() that just frees the eventfs_inode
eventfs: Test for ei->is_freed when accessing ei->dentry
eventfs: Save ownership and mode
----
fs/tracefs/event_inode.c | 217 +++++++++++++++++++++++++++++++++++++++++------
fs/tracefs/internal.h | 19 ++++-
2 files changed, 208 insertions(+), 28 deletions(-)
next reply other threads:[~2023-10-31 19:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 19:31 Steven Rostedt [this message]
2023-10-31 19:31 ` [PATCH v4 1/3] eventfs: Have a free_ei() that just frees the eventfs_inode Steven Rostedt
2023-10-31 19:31 ` [PATCH v4 2/3] eventfs: Test for ei->is_freed when accessing ei->dentry Steven Rostedt
2023-10-31 19:31 ` [PATCH v4 3/3] eventfs: Save ownership and mode Steven Rostedt
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=20231031193109.018322397@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
/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).