Received: by 2002:a05:6a10:6006:0:0:0:0 with SMTP id w6csp1536891pxa; Fri, 28 Aug 2020 15:51:05 -0700 (PDT) X-Google-Smtp-Source: ABdhPJySERjUtMr/jm+kHhn3tb3Jlji4249yqbGtDSJcHuDePEJwqzlTkY7JmVwRRMzYuRAaXgMk X-Received: by 2002:a05:6402:1b02:: with SMTP id by2mr980094edb.95.1598655065510; Fri, 28 Aug 2020 15:51:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1598655065; cv=none; d=google.com; s=arc-20160816; b=Fw3B0Cn70u6gITpk+a997vrroyodj7HkZQXjU80p5svymVtOWxDM0t8NCtfL5ZjZMW yXiYWsx38Uso+aFssZKcGzunjC+z+KkSGm6olFyE7DOIkeSbXMrFWRFO4FgtZPF64prz 2Hc0PngptakXPU4PXBwbQzZWYVW8LhVSoYXiEfL4bawAZzcT0scTqJZvqph6JbIJQXpi sblD8pfkw+X0TYI0kTDCPdaGxDJD5ndOQr5MsAMJ+MyPkRcIYWrgWZ21lcJUaZXegEOj VMl1GKJpx4Pb+YSrNao3DKP/rxvcE2IlmB/ECsZ2QfoA8eXLVD56FOsgGyBy8qNbJCry s2iQ== 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:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date; bh=sZD6yEUJVb3JhsA4WiMNt++mHbE0sHODQbN7yxR4yS8=; b=BsgVr6ko+vx+Xt5/uehWYbda4yvfV+C/pV0gFZLMLgQiyYJl3YcPxB/+v65qcq7Cqb OxWPXySGoU5dgfNpcx0HW2tWFc8tmvB2rPlIm2G+wh3Nbl9kAZMpr4IISepnl+eagkTa 0o/29VVQqWV+WSfmTysPI4OZ0aAvRSwEkjbRYh2luHQfVNEm0ScFPLJhH6gCkjQeBitA oacWcwhtgiA0ETUoCCZK3Rvzc4WVFRkhScy6oiHv4YxWNPvm2TooWn+z6VoIYNDGylkZ 4Txmra9Uccqpw3yZbd9pyzYqisC8YQmzM8uCStNVgD+pVqaV6nVA8mNEMWqxh2MUiXnz 3IAQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id bl4si612875ejb.579.2020.08.28.15.50.42; Fri, 28 Aug 2020 15:51:05 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726952AbgH1WuD (ORCPT + 99 others); Fri, 28 Aug 2020 18:50:03 -0400 Received: from mail.kernel.org ([198.145.29.99]:56736 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726928AbgH1Wt6 (ORCPT ); Fri, 28 Aug 2020 18:49:58 -0400 Received: from oasis.local.home (cpe-66-24-58-225.stny.res.rr.com [66.24.58.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id E6E44208A9; Fri, 28 Aug 2020 22:49:56 +0000 (UTC) Date: Fri, 28 Aug 2020 18:49:55 -0400 From: Steven Rostedt To: Wen Gong Cc: linux-kernel@vger.kernel.org, Ingo Molnar , Andrew Morton , Alexei Starovoitov , linux-kernel-owner@vger.kernel.org, ath10k@lists.infradead.org, ath11k@lists.infradead.org, abhishekpandit@google.com, briannorris@google.com, drinkcat@google.com, tientzu@google.com Subject: Re: [for-next][PATCH 2/2] tracing: Use temp buffer when filtering events Message-ID: <20200828184955.6de9b54e@oasis.local.home> In-Reply-To: References: <20160504135202.422290539@goodmis.org> <20160504135241.308454993@goodmis.org> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 28 Aug 2020 15:53:06 +0800 Wen Gong wrote: > this patch commit id is : 0fc1b09ff1ff404ddf753f5ffa5cd0adc8fdcdc9 which > has upstream. > > how much size is the per cpu buffer? > seems it is initilized in trace_buffered_event_enable, > it is only 1 page size as below: > void trace_buffered_event_enable(void) > { > ... > for_each_tracing_cpu(cpu) { > page = alloc_pages_node(cpu_to_node(cpu), > GFP_KERNEL | __GFP_NORETRY, 0); > If the size of buffer to trace is more than 1 page, such as 46680, then > it trigger kernel crash/panic in my case while run trace-cmd. > After debugging, the trace_file->flags in > trace_event_buffer_lock_reserve is 0x40b while run trace-cmd, and it is > 0x403 while collecting ftrace log. > > Is it have any operation to disable this patch dynamically? It shouldn't be disabled, this is a bug that needs to be fixed. Also, if an event is more than a page, it wont be saved in the ftrace ring buffer, as events are limited by page size minus the headers. -- Steve