From: Ingo Molnar <mingo@elte.hu>
To: Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Paul Mackerras <paulus@samba.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Clark Williams <williams@redhat.com>,
John Kacur <jkacur@redhat.com>
Subject: Re: [PATCH] perf_event: mount debugfs automatically
Date: Mon, 28 Dec 2009 08:44:26 +0100 [thread overview]
Message-ID: <20091228074426.GA20039@elte.hu> (raw)
In-Reply-To: <4B383DE3.3070702@cn.fujitsu.com>
* Xiao Guangrong <xiaoguangrong@cn.fujitsu.com> wrote:
> Mount debugfs automatically if it's not mounted, umount it
> when programme exit
>
> Signed-off-by: Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>
> ---
> tools/perf/perf.c | 10 +++++++++-
> tools/perf/util/debugfs.c | 16 +++++++---------
> tools/perf/util/debugfs.h | 2 +-
> 3 files changed, 17 insertions(+), 11 deletions(-)
I'm not sure that's a good idea. What happens if two perf tools are running in
parallel:
perf report #1 start
perf report #2 start
perf report #2 exit [umount debugfs]
perf report #2 tries to open /debug file: kaboom
perf report #2 exit
But your idea is sound if we only do the first half: we should mount it under
/sys/kernel/debug/ if it's not mounted already [and that directory is
available], and leave it mounted there.
Furthermore please not that we must not mount it under any other path -
mounting is always a dangerous operation because it changes the VFS namespace.
For example some system might have some local files under /debug for whatever
reason, we must not over-mount it and potentially destroy data because we'd
confuse an app that writes into /debug. /sys/kernel/debug/ is a fair game to
mount into OTOH.
(and even then we should just leave it mounted and never umount it.)
Thanks,
Ingo
next prev parent reply other threads:[~2009-12-28 7:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-28 5:10 [PATCH] perf_event: mount debugfs automatically Xiao Guangrong
2009-12-28 7:44 ` Ingo Molnar [this message]
2009-12-28 8:02 ` Xiao Guangrong
2009-12-28 8:06 ` Ingo Molnar
2009-12-28 8:47 ` [PATCH v2 1/3] perf tools: " Xiao Guangrong
2009-12-28 8:48 ` [PATCH 2/3] perf trace: cleanup find_debugfs() Xiao Guangrong
2009-12-28 8:49 ` [PATCH 3/3] perf trace: fix forgetting close file/dir Xiao Guangrong
2009-12-28 10:09 ` [tip:perf/core] perf trace: Fix forgotten close of file/dir tip-bot for Xiao Guangrong
2009-12-28 10:09 ` [tip:perf/core] perf trace: Clean up find_debugfs() tip-bot for Xiao Guangrong
2009-12-28 10:09 ` [tip:perf/core] perf tools: Mount debugfs automatically tip-bot for Xiao Guangrong
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=20091228074426.GA20039@elte.hu \
--to=mingo@elte.hu \
--cc=fweisbec@gmail.com \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=williams@redhat.com \
--cc=xiaoguangrong@cn.fujitsu.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