From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0D399C43457 for ; Wed, 14 Oct 2020 16:00:05 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 971452222F for ; Wed, 14 Oct 2020 16:00:04 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=mg.codeaurora.org header.i=@mg.codeaurora.org header.b="rGBdRuMI" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727670AbgJNQAB (ORCPT ); Wed, 14 Oct 2020 12:00:01 -0400 Received: from z5.mailgun.us ([104.130.96.5]:20164 "EHLO z5.mailgun.us" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726496AbgJNQAB (ORCPT ); Wed, 14 Oct 2020 12:00:01 -0400 DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=mg.codeaurora.org; q=dns/txt; s=smtp; t=1602691200; h=Message-ID: References: In-Reply-To: Subject: Cc: To: From: Date: Content-Transfer-Encoding: Content-Type: MIME-Version: Sender; bh=/WzKeTICSrDP4+lS0iIdtalkTU8mPAd7+F46GS5omvY=; b=rGBdRuMIivozRN7IG656/q2ISZoVfpSHi7LZ13MLIoTzVnc5IBSx+d6plxX1D3aWXHqA42OK qQhNvgzPX84ToNetZ5bjn3OnNZ9qGsGf5TgWriTEeg9UhlyTA6OKdoY6XG+uGbn63ePmhAtm 6XpqAHAtpSeFDc6KRhCIcLMNUJE= X-Mailgun-Sending-Ip: 104.130.96.5 X-Mailgun-Sid: WyI1MzIzYiIsICJsaW51eC1hcm0tbXNtQHZnZXIua2VybmVsLm9yZyIsICJiZTllNGEiXQ== Received: from smtp.codeaurora.org (ec2-35-166-182-171.us-west-2.compute.amazonaws.com [35.166.182.171]) by smtp-out-n06.prod.us-west-2.postgun.com with SMTP id 5f872052f9168450eaef0027 (version=TLS1.2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256); Wed, 14 Oct 2020 15:59:14 GMT Sender: saiprakash.ranjan=codeaurora.org@mg.codeaurora.org Received: by smtp.codeaurora.org (Postfix, from userid 1001) id 3A763C43387; Wed, 14 Oct 2020 15:59:14 +0000 (UTC) Received: from mail.codeaurora.org (localhost.localdomain [127.0.0.1]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: saiprakash.ranjan) by smtp.codeaurora.org (Postfix) with ESMTPSA id 6CAD6C433F1; Wed, 14 Oct 2020 15:59:13 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Wed, 14 Oct 2020 21:29:13 +0530 From: Sai Prakash Ranjan To: Suzuki K Poulose Cc: mathieu.poirier@linaro.org, mike.leach@linaro.org, coresight@lists.linaro.org, swboyd@chromium.org, linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, denik@google.com, leo.yan@linaro.org, peterz@infradead.org Subject: Re: [PATCH 1/2] coresight: tmc-etf: Fix NULL ptr dereference in tmc_enable_etf_sink_perf() In-Reply-To: <707b7860-0daa-d3e3-1f0f-17e1b05feae2@arm.com> References: <5bbb2d35-3e56-56d7-4722-bf34c5efa2fb@arm.com> <9fa4fcc25dac17b343d151a9d089b48c@codeaurora.org> <707b7860-0daa-d3e3-1f0f-17e1b05feae2@arm.com> Message-ID: <5ad6acdc69c1c2e1e17f5c701a09b7e1@codeaurora.org> X-Sender: saiprakash.ranjan@codeaurora.org User-Agent: Roundcube Webmail/1.3.9 Precedence: bulk List-ID: X-Mailing-List: linux-arm-msm@vger.kernel.org On 2020-10-14 18:46, Suzuki K Poulose wrote: > On 10/14/2020 10:36 AM, Sai Prakash Ranjan wrote: >> On 2020-10-13 22:05, Suzuki K Poulose wrote: >>> On 10/07/2020 02:00 PM, Sai Prakash Ranjan wrote: >>>> There was a report of NULL pointer dereference in ETF enable >>>> path for perf CS mode with PID monitoring. It is almost 100% >>>> reproducible when the process to monitor is something very >>>> active such as chrome and with ETF as the sink and not ETR. >>>> Currently in a bid to find the pid, the owner is dereferenced >>>> via task_pid_nr() call in tmc_enable_etf_sink_perf() and with >>>> owner being NULL, we get a NULL pointer dereference. >>>> >>>> Looking at the ETR and other places in the kernel, ETF and the >>>> ETB are the only places trying to dereference the task(owner) >>>> in tmc_enable_etf_sink_perf() which is also called from the >>>> sched_in path as in the call trace. Owner(task) is NULL even >>>> in the case of ETR in tmc_enable_etr_sink_perf(), but since we >>>> cache the PID in alloc_buffer() callback and it is done as part >>>> of etm_setup_aux() when allocating buffer for ETR sink, we never >>>> dereference this NULL pointer and we are safe. So lets do the >>> >>> The patch is necessary to fix some of the issues. But I feel it is >>> not complete. Why is it safe earlier and not later ? I believe we are >>> simply reducing the chances of hitting the issue, by doing this >>> earlier than >>> later. I would say we better fix all instances to make sure that the >>> event->owner is valid. (e.g, I can see that the for kernel events >>> event->owner == -1 ?) >>> >>> struct task_struct *tsk = READ_ONCE(event->owner); >>> >>> if (!tsk || is_kernel_event(event)) >>>    /* skip ? */ >>> >> >> Looking at it some more, is_kernel_event() is not exposed >> outside events core and probably for good reason. Why do >> we need to check for this and not just tsk? > > Because the event->owner could be : > > = NULL > = -1UL // kernel event > = valid. > Yes I understood that part, but here we were trying to fix the NULL pointer dereference right and hence the question as to why we need to check for kernel events? I am no expert in perf but I don't see anywhere in the kernel checking for is_kernel_event(), so I am a bit skeptical if exporting that is actually right or not. Thanks, Sai -- QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation