From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH 0/4] eventfs: Simplify the permissions logic
Date: Wed, 22 May 2024 12:49:42 -0400 [thread overview]
Message-ID: <20240522164942.590663963@goodmis.org> (raw)
While debugging the failure of the ownership test failing on the
second run again, I ended up greatly simplifying the eventfs code
with respect to the permissions, only to discover that the bug was
elsewhere[1].
But because of the great diff-stat that this produced, not to mention
the simplifying of the code, I'm going to try to get this into this
merge window.
[1] https://lore.kernel.org/linux-trace-kernel/20240522124504.28982867@gandalf.local.home/
Steven Rostedt (Google) (4):
eventfs: Consolidate the eventfs_inode update in eventfs_get_inode()
eventfs: Remove getattr and permission callbacks
eventfs: Cleanup permissions in creation of inodes
eventfs: Do not use attributes for events directory
----
fs/tracefs/event_inode.c | 172 +++++++++++++----------------------------------
1 file changed, 46 insertions(+), 126 deletions(-)
next reply other threads:[~2024-05-22 16:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 16:49 Steven Rostedt [this message]
2024-05-22 16:49 ` [PATCH 1/4] eventfs: Consolidate the eventfs_inode update in eventfs_get_inode() Steven Rostedt
2024-05-22 16:49 ` [PATCH 2/4] eventfs: Remove getattr and permission callbacks Steven Rostedt
2024-05-22 16:49 ` [PATCH 3/4] eventfs: Cleanup permissions in creation of inodes Steven Rostedt
2024-05-22 16:49 ` [PATCH 4/4] eventfs: Do not use attributes for events directory 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=20240522164942.590663963@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®