public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	AnishMulay <anishm7030@gmail.com>,
	David Carlier <devnexen@gmail.com>
Subject: [GIT PULL] tracefs: Updates for v7.1
Date: Tue, 14 Apr 2026 07:57:53 -0400	[thread overview]
Message-ID: <20260414075753.2a036358@robin> (raw)


Linus,

tracefs updates for 7.1:

- Simplify error handling with guards()

  Use guards() to simplify the handling of releasing locks in exit paths.

- Use dentry name snapshots instead of allocation

  Instead of allocating a temp buffer to store the dentry name to use in
  mkdir() and rmdir() use take_dentry_name_snapshot().

- Fix default permissions not being applied at boot

  The default permissions for tracefs was 0700 to only allow root having
  access. But after a change to fix other mount options the update to
  permissions ignored the defined default and used the system default of
  0755. This is a regression and is fixed.


Please pull the latest tracefs-v7.1 tree, which can be found at:


  git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
tracefs-v7.1

Tag SHA1: e5d58661152be92434e3ef6ebcd4e9b4ceaec6dd
Head SHA1: e8368d1f4bedbb0cce4cfe33a1d2664bb0fd4f27


AnishMulay (1):
      tracefs: Use dentry name snapshots instead of heap allocation

David Carlier (1):
      tracefs: Fix default permissions not being applied on initial mount

Steven Rostedt (1):
      eventfs: Simplify code using guard()s

----
 fs/tracefs/event_inode.c | 96 ++++++++++++++++++------------------------------
 fs/tracefs/inode.c       | 40 +++++---------------
 2 files changed, 45 insertions(+), 91 deletions(-)
---------------------------

             reply	other threads:[~2026-04-14 11:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-14 11:57 Steven Rostedt [this message]
2026-04-14 13:42 ` [GIT PULL] tracefs: Updates for v7.1 Steven Rostedt
2026-04-16  0:51 ` pr-tracker-bot

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=20260414075753.2a036358@robin \
    --to=rostedt@goodmis.org \
    --cc=anishm7030@gmail.com \
    --cc=devnexen@gmail.com \
    --cc=linux-kernel@vger.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