Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp4371143imm; Mon, 17 Sep 2018 12:44:12 -0700 (PDT) X-Google-Smtp-Source: ANB0VdbkLCRdGRObegM909yLIds54jyfFPYfSHN3Yi2CEM/Q4X2MaWumYBnYvrcQMhNyjWmGxiLe X-Received: by 2002:a62:cc83:: with SMTP id j3-v6mr27490229pfk.255.1537213452315; Mon, 17 Sep 2018 12:44:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1537213452; cv=none; d=google.com; s=arc-20160816; b=M/adL0fYBMZ27DfxGUB6GfCAaAIqTSNX9CKcJi6DEPjQKxjpOpQ/DYNjPKSFq15k7V RJE6xTvGJm23/Il2n0HbI7VeDOTHz2LlZurWYNwB2Q5tnVXaLZfG5v14kiFdvFOle1Mm T2+qwInsCysoiVZsHijRSUYKm2KJjb8hSAYlKC0n2Aeo8ZQGDOyjHng5Y0iLJh/sOy+h 0QGB9DRV+xrFOzrXZbpIWCD6zRpgLEbs38R9xO0EndX1a2DIEezg9/SPlRlEKnw6Xvmt zvP4oN4Zx1ep0QbthKfHInfgt9FEZYmllJw6Z8BO/FFvKuYa+3490R89+dNpA5PhiZv9 4iMQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dmarc-filter :dkim-signature:dkim-signature; bh=YnfAfqHebWvVRhqhN/+AaGaTfPBsdl8RS6jDCN9fG1M=; b=ePen/8oCsqRx9xztD7TKxRyLP/2aM/oVOxiycSJ7BCNTD1W2RU06R4p2KjyiQCDfo7 f/ImGGmQjvF1hOEtWOLcl4d1KuOMnA4s2HDM8MW9vGcGRZKLR/RZSXzVGesvllB6QvWB 1tTdR1zQ7vWQU/5DIB/U45/d0eF7dd57haAMzCCEN3T03rBK2O3sHiL6MDH1gir+XjGF 0vKxj5xDrhEccpV+5bFK0g9+3NWGNyeuMnMc662XMUyNVZTkd3m7PXvFZIpeaALFG5Uf zl6XpuVeALIMm3sAeu80reedbKTw1unUe1Dkdg4IkDnI++hHTJK9W72q8laqzpT4ZEMq fjFQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@codeaurora.org header.s=default header.b=D8DAm25o; dkim=pass header.i=@codeaurora.org header.s=default header.b=oPMeRMKP; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id k1-v6si15958015pld.424.2018.09.17.12.43.56; Mon, 17 Sep 2018 12:44:12 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@codeaurora.org header.s=default header.b=D8DAm25o; dkim=pass header.i=@codeaurora.org header.s=default header.b=oPMeRMKP; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728236AbeIRBMf (ORCPT + 99 others); Mon, 17 Sep 2018 21:12:35 -0400 Received: from smtp.codeaurora.org ([198.145.29.96]:57846 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727089AbeIRBMf (ORCPT ); Mon, 17 Sep 2018 21:12:35 -0400 Received: by smtp.codeaurora.org (Postfix, from userid 1000) id 21F1960C54; Mon, 17 Sep 2018 19:43:48 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1537213428; bh=9Vd6kliHS+GxDvROhrELPpl3K9gR/Xr9YdSczQC2Np4=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=D8DAm25oyq2HsQEQqrgIVKZTckbKMMwgXv39rV6BZ3Yo39YGimPeJEJZPx1eqPYBB DgPdEO3rc3fA0lIO8UwRJ/bpvQPCqBzGY1ex6Upbm+Y57Q0IAfkRoj8ck1aFZNfKQp L+uoEfmjMTegKeRmkn0nh24IEcBXLWmghJmA8JLA= X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on pdx-caf-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.8 required=2.0 tests=ALL_TRUSTED,BAYES_00, DKIM_SIGNED,T_DKIM_INVALID autolearn=no autolearn_force=no version=3.4.0 Received: from [192.168.43.47] (unknown [27.59.117.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: saiprakash.ranjan@smtp.codeaurora.org) by smtp.codeaurora.org (Postfix) with ESMTPSA id E2D50602A7; Mon, 17 Sep 2018 19:43:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1537213427; bh=9Vd6kliHS+GxDvROhrELPpl3K9gR/Xr9YdSczQC2Np4=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=oPMeRMKPEizLi0RgMV10g9nadOTKmkZyuF/3XEfKLO9oIWzDd9zyi7vrbgccI3UjA eztVTSmwRTZFQuyEcEj3Di7zWqpSAIMQGf+oUpmYk3VU/ZEpicJq0jOLTM8MprM+kU tTk4N7RiqD60rORSZRntqS4xTVmokZSCiRi9kY20= DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org E2D50602A7 Authentication-Results: pdx-caf-mail.web.codeaurora.org; dmarc=none (p=none dis=none) header.from=codeaurora.org Authentication-Results: pdx-caf-mail.web.codeaurora.org; spf=none smtp.mailfrom=saiprakash.ranjan@codeaurora.org Subject: Re: [PATCH 2/6] pstore: Add event tracing support To: Stephen Boyd , Anton Vorontsov , Arnd Bergmann , Catalin Marinas , Colin Cross , Ingo Molnar , Jason Baron , Jim Cromie , Joe Perches , Joel Fernandes , Kees Cook , Laura Abbott , Masami Hiramatsu , Rob Herring , Steven Rostedt , Tony Luck , Will Deacon , devicetree@vger.kernel.org Cc: Rajendra Nayak , Vivek Gautam , Sibi Sankar , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, Greg Kroah-Hartman , Ingo Molnar , Tom Zanussi , Prasad Sodagudi , tsoni@codeaurora.org, Bryan Huntsman , Tingwei Zhang References: <444d7b13-2653-ba0e-e9e6-a448fded2a77@codeaurora.org> <153720590027.119890.15984895820368075914@swboyd.mtv.corp.google.com> From: Sai Prakash Ranjan Message-ID: <03d47d84-a237-a94e-04ee-4447d8620697@codeaurora.org> Date: Tue, 18 Sep 2018 01:13:30 +0530 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <153720590027.119890.15984895820368075914@swboyd.mtv.corp.google.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 9/17/2018 11:08 PM, Stephen Boyd wrote: > Quoting Sai Prakash Ranjan (2018-09-11 03:46:01) >> On 9/9/2018 1:57 AM, Sai Prakash Ranjan wrote: >>> +void notrace pstore_event_call(struct trace_event_buffer *fbuffer) >>> +{ >>> + struct trace_iterator *iter; >>> + struct trace_seq *s; >>> + struct trace_event_call *event_call; >>> + struct pstore_record record; >>> + struct trace_event *event; >>> + struct seq_buf *seq; >>> + unsigned long flags; >>> + >>> + if (!psinfo) >>> + return; >>> + >>> + if (unlikely(oops_in_progress)) >>> + return; >>> + >>> + pstore_record_init(&record, psinfo); >>> + record.type = PSTORE_TYPE_EVENT; >>> + >>> + iter = kmalloc(sizeof(*iter), GFP_KERNEL); >>> + if (!iter) >>> + return; >>> + >>> + event_call = fbuffer->trace_file->event_call; >>> + if (!event_call || !event_call->event.funcs || >>> + !event_call->event.funcs->trace) >>> + goto fail_event; >>> + >>> + event = &fbuffer->trace_file->event_call->event; >>> + >>> + spin_lock_irqsave(&psinfo->buf_lock, flags); >>> + >>> + trace_seq_init(&iter->seq); >>> + iter->ent = fbuffer->entry; >>> + event_call->event.funcs->trace(iter, 0, event); >>> + trace_seq_putc(&iter->seq, 0); >>> + >>> + if (seq->size > psinfo->bufsize) >>> + seq->size = psinfo->bufsize; >>> + >>> + s = &iter->seq; >>> + seq = &s->seq; >>> + >>> + record.buf = (char *)(seq->buffer); >>> + record.size = seq->len; >>> + psinfo->write(&record); >>> + >>> + spin_unlock_irqrestore(&psinfo->buf_lock, flags); >>> + >>> +fail_event: >>> + kfree(iter); >>> +} >>> + >>> >> >> When tracing sched events on sdm845 mtp, I hit below bug repeatedly. >> Seems like pstore_event_call can be called in atomic context. >> I will respin the below fix in next version of the patch. >> Reviews on other parts would be appreciated, thanks. >> >> diff --git a/fs/pstore/ftrace.c b/fs/pstore/ftrace.c >> index d47dc93ac098..a497cf782ee8 100644 >> --- a/fs/pstore/ftrace.c >> +++ b/fs/pstore/ftrace.c >> @@ -73,6 +73,7 @@ void notrace pstore_event_call(struct >> trace_event_buffer *fbuffer) >> struct trace_event *event; >> struct seq_buf *seq; >> unsigned long flags; >> + gfp_t gfpflags; >> >> if (!psinfo) >> return; >> @@ -83,7 +84,9 @@ void notrace pstore_event_call(struct >> trace_event_buffer *fbuffer) >> pstore_record_init(&record, psinfo); >> record.type = PSTORE_TYPE_EVENT; >> >> - iter = kmalloc(sizeof(*iter), GFP_KERNEL); >> + gfpflags = (in_atomic() || irqs_disabled()) ? GFP_ATOMIC : >> GFP_KERNEL; >> + > Hi Stephen Thanks for the comments. > Do you need to allocate at all? Can you throw the iter on the stack? > Yes since we need to copy the contents to pstore buffer. > Using in_atomic() and irqs_disabled() to figure out if an atomic or a > non-atomic allocation should be used is not a good solution. > I took reference from a similar use by graph_trace_open() which can be called in atomic context via ftrace_dump(). I am open to correct this if there is some other way. Sai -- QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation