From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754915AbbJAJKi (ORCPT ); Thu, 1 Oct 2015 05:10:38 -0400 Received: from mail-wi0-f173.google.com ([209.85.212.173]:38071 "EHLO mail-wi0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751157AbbJAJKf (ORCPT ); Thu, 1 Oct 2015 05:10:35 -0400 Date: Thu, 1 Oct 2015 11:10:31 +0200 From: Ingo Molnar To: Taeung Song Cc: Arnaldo Carvalho de Melo , linux-kernel@vger.kernel.org, jolsa@redhat.com, namhyung@kernel.org, Ingo Molnar , Peter Zijlstra Subject: Re: [PATCH v1] perf report: Fix owner error when reading perf.data Message-ID: <20151001091031.GA6543@gmail.com> References: <1443690214-1194-1-git-send-email-treeze.taeung@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1443690214-1194-1-git-send-email-treeze.taeung@gmail.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Taeung Song wrote: > If perf.data file is owned by some user, > it can't be read even if current user is root. That's intentional: to keep a malicious local user from passing a perf.data to root who does 'perf report' accidentally or in the wrong directory. root can copy or chown it to himself - or we could add some --really-force flag for that. Thanks, Ingo