From: Steven Rostedt <rostedt@goodmis.org>
To: "Zhengyuan Liu" <liuzhengyuan@kylinos.cn>
Cc: "mingo" <mingo@redhat.com>,
"linux-kernel" <linux-kernel@vger.kernel.org>,
"liuzhengyuang521" <liuzhengyuang521@gmail.com>,
"linx.z.chen" <linx.z.chen@intel.com>
Subject: Re: [PATCH] ftrace: fix the file mode of graph tracer and stacktracer
Date: Thu, 8 Feb 2018 22:21:22 -0500 [thread overview]
Message-ID: <20180208222122.5ba7c7fe@vmware.local.home> (raw)
In-Reply-To: <tencent_34C119E628948BE127843C25@qq.com>
On Fri, 9 Feb 2018 10:33:31 +0800
"Zhengyuan Liu" <liuzhengyuan@kylinos.cn> wrote:
> It doesn't affect root writing to those files as root is a super user and
> can access to any write-only files. I just want to make those writable
Ah, I know when I vim a file that's read only, even for root vim will
complain. But there's no complaining with redirection.
I just tried vim on set_graph_function, and yeah, it does complain.
> file to look consistent with others, seeing bellow:
>
> -rw-r--r-- 1 root root set_event_pid
> -rw-r--r-- 1 root root set_ftrace_filter
> -rw-r--r-- 1 root root set_ftrace_notrace
> -rw-r--r-- 1 root root set_ftrace_pid
> -r--r--r-- 1 root root set_graph_function
> -r--r--r-- 1 root root set_graph_notrace
Yeah, I understand.
>
> If this patch makes no sense, just ignore it!
No no, it makes perfect sense. I plan on adding it. But it's not that
important to be included for stable. Expect to see this in 4.17.
Thanks!
-- Steve
prev parent reply other threads:[~2018-02-09 3:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 1:41 [PATCH] ftrace: fix the file mode of graph tracer and stack tracer Zhengyuan Liu
2018-02-08 15:21 ` Steven Rostedt
2018-02-09 2:33 ` [PATCH] ftrace: fix the file mode of graph tracer and stacktracer Zhengyuan Liu
2018-02-09 3:21 ` 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=20180208222122.5ba7c7fe@vmware.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linx.z.chen@intel.com \
--cc=liuzhengyuan@kylinos.cn \
--cc=liuzhengyuang521@gmail.com \
--cc=mingo@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
Powered by JetHome