From: Steven Rostedt <rostedt@goodmis.org>
To: Ondrej Mosnacek <omosnace@redhat.com>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tracing: Fix permissions for the buffer_percent file
Date: Wed, 3 May 2023 12:46:18 -0400 [thread overview]
Message-ID: <20230503124618.3baf9a98@gandalf.local.home> (raw)
In-Reply-To: <20230503140114.3280002-1-omosnace@redhat.com>
On Wed, 3 May 2023 16:01:14 +0200
Ondrej Mosnacek <omosnace@redhat.com> wrote:
> This file defines both read and write operations, yet it is being
> created as read-only. This means that it can't be written to without the
> CAP_DAC_OVERRIDE capability. Fix the permissions to allow root to write
> to it without the need to override DAC perms.
>
> Fixes: 03329f993978 ("tracing: Add tracefs file buffer_percentage")
> Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
Applied. Thanks Ondrej!
-- Steve
prev parent reply other threads:[~2023-05-03 16:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 14:01 [PATCH] tracing: Fix permissions for the buffer_percent file Ondrej Mosnacek
2023-05-03 16:46 ` Steven Rostedt [this message]
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=20230503124618.3baf9a98@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=omosnace@redhat.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).