Received: by 2002:a25:ef43:0:0:0:0:0 with SMTP id w3csp669552ybm; Fri, 29 May 2020 09:19:37 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzhLsONhT9DraE6K5OGzZH8TzSDwj98acSQJ+IZU77GXtCDWSVqSuVgdifBEYdDSeriLtgu X-Received: by 2002:a50:ec8e:: with SMTP id e14mr9152655edr.105.1590769177711; Fri, 29 May 2020 09:19:37 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1590769177; cv=none; d=google.com; s=arc-20160816; b=j4zKIeRhJZl93Ol8a+rjGXn7Jl7lOU8MQjPP2IjYFJ9Xmz2kCTUNgyBShihRb5gyjk mnACqifzKQdSH4XZeqv9ym/2dvS1Z2X38pWO3j4pIqsBN3KX1Yev7J+oq5sG39TmP0dA iLAcxYd+hRZmcrW4+o+lxesQllnFBQliLziPWYeeezyFZ79sKAU5SMnxaTS7d0YB4c+Q S2WtxpBjRqhCkYuGlFvQwec/VDrMowUhk28D3qMvbUzlvPIeB6qXpNC+0/A2dpwy/haP 7eNVvi6RJYGUHG1FiPRREsJNF6dBbx02Mf8TsJVOMgP0TxWhX6EsOq3XYHtdQRlDleeS e1UQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=ZZTNQsLm7+rzlNMHgCCgzCHQBo5dBhmslh5bPqqWk+k=; b=z7BQYVFNT5Vw2d3VAO7Tw+u1X0xqpaxmJzU8cgkkjv/8DbY+FunY291MCDqJCUzT/8 b21oXmrYSaruFzcvZoFz4wcVh5yPXJXT4KH5khAXBQ+/RlnmSWSHlrK4iyvMKx9f9dUS bD8FbXNMJC2mWGZpmskBb2Vq0VYXpKXxjBTYZ1sIL8MjrMu4eJE2cHaxWqxMdHzd0Gst WYV3EPYAx9yMxzH/hzAHqAOUY0fp/LGrELv0IEU2K+RYNMcvgk+qp8DLW2Hp9BdLMQ9c te0Bzuwa7SArBCI8YF03YsZ1IH0Q5r7ELKIaiSS599cHCx2MpvQbYeUfw7lzK6Jzvx21 ujVQ== 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 y14si4079537ejp.357.2020.05.29.09.19.13; Fri, 29 May 2020 09:19:37 -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 S1727008AbgE2QPV convert rfc822-to-8bit (ORCPT + 99 others); Fri, 29 May 2020 12:15:21 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57206 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725601AbgE2QPV (ORCPT ); Fri, 29 May 2020 12:15:21 -0400 Received: from Galois.linutronix.de (Galois.linutronix.de [IPv6:2a0a:51c0:0:12e:550::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 762A2C03E969; Fri, 29 May 2020 09:15:21 -0700 (PDT) Received: from bigeasy by Galois.linutronix.de with local (Exim 4.80) (envelope-from ) id 1jehfC-0000nm-H5; Fri, 29 May 2020 18:15:18 +0200 Date: Fri, 29 May 2020 18:15:18 +0200 From: Sebastian Andrzej Siewior To: Mark Marshall Cc: linux-rt-users , Mark Marshall , thomas.graziadei@omicronenergy.com, Thomas Gleixner , linux-kernel@vger.kernel.org, rostedt@goodmis.org Subject: Re: Kernel crash due to memory corruption with v5.4.26-rt17 and PowerPC e500 Message-ID: <20200529161518.svpxhkeljafbtdz2@linutronix.de> References: <20200529131452.pgj7mx7xaz7n4kz3@linutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8BIT In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2020-05-29 17:38:39 [+0200], Mark Marshall wrote: > Hi Sebastian & list, Hi, > I had assumed that my e-mail had got lost or overlooked, I was meaning to > post a follow up message this week... > > All I could find from the debugging and tracing that we added was that > something was going wrong with the mm data structures somewhere in the > exec code. In the end I just spent a week or two pouring over the diffs > of this code between the versions that I new worked and didn't work. > > I eventually found the culprit. On the working kernel versions there is > a patch called "mm: Protect activate_mm() by preempt_[disable&enable]_rt()". > This is commit f0b4a9cb253a on the V4.19.82-rt30 branch, for instance. > Although the commit message talks about ARM, it seems that we need this for > PowerPC too (I guess, any PowerPC with the "nohash" MMU?). Could you drop me your config, please? I need to dig here a little and I should have seen this on qemu, right? > Could you please add this commit back to the RT branch? I'm not sure how > to find out the history of this commit. For instance, why has it been > removed from the RT patchset? How are these things tracked, generally? I dropped that patch in v5.4.3-rt1. I couldn't reproduce the issue that was documented in the patch and the code that triggered the warning was removed / reworked in commit b5466f8728527 ("ARM: mm: remove IPI broadcasting on ASID rollover") So it looked like no longer needed and then got dropped during the rebase. In order to get it back into the RT queue I need to understand why it is required. What exactly is it fixing. Let me stare at for a littleā€¦ > Best regards, > Mark Sebastian