Received: by 2002:a25:23cc:0:0:0:0:0 with SMTP id j195csp294955ybj; Fri, 8 May 2020 12:02:19 -0700 (PDT) X-Google-Smtp-Source: APiQypKKOO9psxA9TDBP8MaLMbAJlUMiSJBQ+92s9cGPyTtxWwMER/mm0z0kwkYdr4g01kNWayrD X-Received: by 2002:a17:906:e210:: with SMTP id gf16mr3269855ejb.214.1588964539526; Fri, 08 May 2020 12:02:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1588964539; cv=none; d=google.com; s=arc-20160816; b=0uJ4HEXs3kWmH3m9FQHTxO+q0KotharCp48U2JLPh84VO6S65XWlsUD42iXoIo5TaH erQ4eshReqGVqgJ5AlEVpo0+GF1mHCFC+P+Tu7nd3CZRZabyTm21Iw1duDssq6W7cxWu NFnVigwAQB3maRvebR6WGzBuyCwy6vSud5JFYd32uAlPNYDXbYhhm0+FSSaHWJNGTPb5 4UIUN5BI9+bMRpeGc6put740LfCY/dqcosSGKNSrJnepGlbZg8gkntYVsJ7M0FTrFD8R Uo0OJgEN863huTg1El56DEV6Y4tS9io7DJk1SXrR7u6/F0nDprRAZr0yKuLnUZBw/Ber Q5JA== 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=Xh2fB8FpesFEINWRJtwP0EN0nbH13RDCukpQKBikGgg=; b=SSP7TYY3fUznTIhPVAWdo5T1s3awJAWHEdCKo+oZy6zW0asRTNn1UGw7FJUzu6yMLA WL2aFOq555TgcpKGOaw2z5zXmEFcMYRojZg5Jd4nEfaQb1SOCsWcOTcXYoZvz6kC/8Ey X6KPMyitACHHKshuYtJwfVkVamrDrPUHrj8zFZcjeLCcitw5K6yYnhDZqAebwvP8hKj+ DeD5eBhMIPIs3l+gagA8LL5MLyAJLWnXxMvIsZdZdx2fcq9exNwQla/DWBQ5UYFgNSlq 61axWIQZHsKwIBoO/SD8bhz5kaR20KBRmcTnATHzJd4WfFeWtyWG7APUWPVMGDDrRgMC Ak3w== 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 dc26si797956edb.32.2020.05.08.12.01.52; Fri, 08 May 2020 12:02:19 -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 S1727082AbgEHS61 (ORCPT + 99 others); Fri, 8 May 2020 14:58:27 -0400 Received: from mail.kernel.org ([198.145.29.99]:38382 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726767AbgEHS61 (ORCPT ); Fri, 8 May 2020 14:58:27 -0400 Received: from gandalf.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 8924D2083B; Fri, 8 May 2020 18:58:25 +0000 (UTC) Date: Fri, 8 May 2020 14:58:22 -0400 From: Steven Rostedt To: Joerg Roedel Cc: x86@kernel.org, hpa@zytor.com, Dave Hansen , Andy Lutomirski , Peter Zijlstra , rjw@rjwysocki.net, Arnd Bergmann , Andrew Morton , Vlastimil Babka , Michal Hocko , Joerg Roedel , linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org, linux-arch@vger.kernel.org, linux-mm@kvack.org Subject: Re: [RFC PATCH 6/7] mm: Remove vmalloc_sync_(un)mappings() Message-ID: <20200508145822.07fcc32b@gandalf.local.home> In-Reply-To: <20200508144043.13893-7-joro@8bytes.org> References: <20200508144043.13893-1-joro@8bytes.org> <20200508144043.13893-7-joro@8bytes.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, 8 May 2020 16:40:42 +0200 Joerg Roedel wrote: > From: Joerg Roedel > > These functions are not needed anymore because the vmalloc and ioremap > mappings are now synchronized when they are created or teared down. > > Remove all callers and function definitions. > > Signed-off-by: Joerg Roedel > You'll need to fold this into this patch, as my patch has already hit Linus's tree. But I applied your whole series and I'm not able to reproduce the bug. Tested-by: Steven Rostedt (VMware) -- Steve diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c index 29615f15a820..1424a89193c6 100644 --- a/kernel/trace/trace.c +++ b/kernel/trace/trace.c @@ -8526,19 +8526,6 @@ static int allocate_trace_buffers(struct trace_array *tr, int size) */ allocate_snapshot = false; #endif - - /* - * Because of some magic with the way alloc_percpu() works on - * x86_64, we need to synchronize the pgd of all the tables, - * otherwise the trace events that happen in x86_64 page fault - * handlers can't cope with accessing the chance that a - * alloc_percpu()'d memory might be touched in the page fault trace - * event. Oh, and we need to audit all other alloc_percpu() and vmalloc() - * calls in tracing, because something might get triggered within a - * page fault trace event! - */ - vmalloc_sync_mappings(); - return 0; }