public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
	acme@redhat.com, fweisbec@gmail.com, penberg@kernel.org,
	peterz@infradead.org, tglx@linutronix.de, mingo@elte.hu
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:perf/urgent] perf symbols: Check '/tmp/perf-' symbol file ownership
Date: Wed, 10 Aug 2011 22:51:43 -0600	[thread overview]
Message-ID: <4E435FDF.9030304@gmail.com> (raw)
In-Reply-To: <tip-981c1252691f4b855f2bb47ea93fb6052ea3aee2@git.kernel.org>

On 08/10/2011 03:48 AM, tip-bot for Pekka Enberg wrote:
> Commit-ID:  981c1252691f4b855f2bb47ea93fb6052ea3aee2
> Gitweb:     http://git.kernel.org/tip/981c1252691f4b855f2bb47ea93fb6052ea3aee2
> Author:     Pekka Enberg <penberg@kernel.org>
> AuthorDate: Tue, 9 Aug 2011 22:54:18 +0300
> Committer:  Arnaldo Carvalho de Melo <acme@redhat.com>
> CommitDate: Tue, 9 Aug 2011 15:23:08 -0300
> 
> perf symbols: Check '/tmp/perf-' symbol file ownership
> 
> The external symbol files are generated by JIT compilers, for example, but we
> need to make sure they're ours before injecting them to 'perf report'.
> 
> Requested-by: Ingo Molnar <mingo@elte.hu>
> Cc: Frederic Weisbecker <fweisbec@gmail.com>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Link: http://lkml.kernel.org/r/1312919658-17158-1-git-send-email-penberg@kernel.org
> Signed-off-by: Pekka Enberg <penberg@kernel.org>
> Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
> ---
>  tools/perf/util/symbol.c |   11 +++++++++++
>  1 files changed, 11 insertions(+), 0 deletions(-)
> 
> diff --git a/tools/perf/util/symbol.c b/tools/perf/util/symbol.c
> index eec1963..a8b5371 100644
> --- a/tools/perf/util/symbol.c
> +++ b/tools/perf/util/symbol.c
> @@ -1504,6 +1504,17 @@ int dso__load(struct dso *dso, struct map *map, symbol_filter_t filter)
>  	dso->adjust_symbols = 0;
>  
>  	if (strncmp(dso->name, "/tmp/perf-", 10) == 0) {
> +		struct stat st;
> +
> +		if (stat(dso->name, &st) < 0)
> +			return -1;
> +
> +		if (st.st_uid && (st.st_uid != geteuid())) {
> +			pr_warning("File %s not owned by current user or root, "
> +				"ignoring it.\n", dso->name);
> +			return -1;
> +		}

Is the force option relevant here -- similar to perf_session__open()?

David

> +
>  		ret = dso__load_perf_map(dso, map, filter);
>  		dso->symtab_type = ret > 0 ? SYMTAB__JAVA_JIT :
>  					      SYMTAB__NOT_FOUND;
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

  reply	other threads:[~2011-08-11  4:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-09 19:54 [PATCH] perf tools: Check '/tmp/perf-' symbol file ownership Pekka Enberg
2011-08-09 19:55 ` Pekka Enberg
2011-08-10  9:48 ` [tip:perf/urgent] perf symbols: " tip-bot for Pekka Enberg
2011-08-11  4:51   ` David Ahern [this message]
2011-08-12 17:34     ` Pekka Enberg

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=4E435FDF.9030304@gmail.com \
    --to=dsahern@gmail.com \
    --cc=acme@redhat.com \
    --cc=fweisbec@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mingo@redhat.com \
    --cc=penberg@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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