Received: by 2002:a05:6359:6284:b0:131:369:b2a3 with SMTP id se4csp4677770rwb; Tue, 8 Aug 2023 12:00:09 -0700 (PDT) X-Google-Smtp-Source: AGHT+IGnAE7EWxy3NGf3hYKK98B+PR1EvBD7eZIFx1jNWTX+Hj220KierzfbT+KO8be7lqZi4F4q X-Received: by 2002:a05:6a00:a01:b0:687:94c5:6d9d with SMTP id p1-20020a056a000a0100b0068794c56d9dmr413723pfh.30.1691521209483; Tue, 08 Aug 2023 12:00:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1691521209; cv=none; d=google.com; s=arc-20160816; b=qaYsTa6Hx2arsANTzUGCdqDfipf6j97qbOYyoEgVP7CqBVjkRclSlUvjfE3WJVLYkP 1WSeWiZbs5/N5ugBVmUqUZ3mpm/1lAOYeJ0SZ6cWwhOEMWaQZt+mL7aiJ8Sxu/bzEYcJ Z9cf2Q4col5YfLrznNYSNPM6KkvmQ+Yanqei7SLUi092wUVa4NWsg8ctMi80hV6n8nIj qHFPW3euU3WCyPAFlhzb3u2JiwBveohNrRGgBYZvaTrht+s09gjn9TsRszWw5Tjq607r S3fie4FIpyGMf2FtELtUqpB1+Omt4SmDnA53qZIvHMozlfkfPqdlKPV30x9mTLcc++Pp 16vA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:reply-to:user-agent :mime-version:date:message-id; bh=y1pKcU+Ky3RWTpWmZZX6JLpa038zpA29qYU8dk1fcLI=; fh=snNAWU/B4tSvyp7LcPAbOMdEwdZEEt/tRiKN30IYH9Q=; b=l5FWJ4h0/YMDCfCtnjqUgdTmb++VXk+pC7xwCRBHjWoSMyflYrtELvXyWzFLHJMkZG c1OgTeQIqP+49NOaCtngRuUmBTzMPmvGqZQehSxTxxiBiawqcb/+CLL56CmwNkiQwgbA rBXdB7cSOOa/r+NU4RZQS98Nc4D1a4zQzqPXb4KjuWvOzeVtgCB2OVZbcbAjrRuUYadC TsiQX4ukPVKD2VQ2wtHs/+ltVWTbYKGhiIC8G7/+lusUbBv6hyL5PW5949aEwF/J6vuL COF4uc1UakSHOicdOSAs+8cQKs1AyTpaJ+u8v7DFeOt2t6bRSpOEn9kFKA/xptBWKCZc r/wQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id bs3-20020a632803000000b005651147ebcasi1731021pgb.363.2023.08.08.11.59.57; Tue, 08 Aug 2023 12:00:09 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235802AbjHHS3b (ORCPT + 99 others); Tue, 8 Aug 2023 14:29:31 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60338 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235911AbjHHS3P (ORCPT ); Tue, 8 Aug 2023 14:29:15 -0400 Received: from wp530.webpack.hosteurope.de (wp530.webpack.hosteurope.de [80.237.130.52]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3F52A249B1 for ; Tue, 8 Aug 2023 10:44:54 -0700 (PDT) Received: from [185.238.219.21] (helo=[192.168.44.45]); authenticated by wp530.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) id 1qTFeQ-0003sC-03; Tue, 08 Aug 2023 07:53:02 +0200 Message-ID: <88bb7f30-cbfe-feb4-1101-b7c98843652d@leemhuis.info> Date: Tue, 8 Aug 2023 07:52:43 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Reply-To: Linux regressions mailing list Subject: Re: [PATCH v2 12/32] mm/vmalloc: vmalloc_to_page() use pte_offset_kernel() Content-Language: en-US, de-DE To: Mark Brown , Will Deacon Cc: Hugh Dickins , Lorenzo Stoakes , Andrew Morton , Mike Kravetz , Mike Rapoport , "Kirill A. Shutemov" , Matthew Wilcox , David Hildenbrand , Suren Baghdasaryan , Qi Zheng , Yang Shi , Mel Gorman , Peter Xu , Peter Zijlstra , Yu Zhao , Alistair Popple , Ralph Campbell , Ira Weiny , Steven Price , SeongJae Park , Huang Ying , Naoya Horiguchi , Christophe Leroy , Zack Rusin , Jason Gunthorpe , Axel Rasmussen , Anshuman Khandual , Pasha Tatashin , Miaohe Lin , Minchan Kim , Christoph Hellwig , Song Liu , Thomas Hellstrom , Ryan Roberts , linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org, Linux kernel regressions list References: <696386a-84f8-b33c-82e5-f865ed6eb39@google.com> <42279f1f-7b82-40dc-8546-86171018729c@sirena.org.uk> <901ae88d-ad0c-4e9d-b199-f1566cc62a00@lucifer.local> <977ddee4-35f0-fcd1-2fd-1c3057e7ea2a@google.com> <591b5253-47f0-440c-84b6-7786ff59667d@sirena.org.uk> <20230720103227.GB11034@willie-the-truck> From: "Linux regression tracking (Thorsten Leemhuis)" In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-bounce-key: webpack.hosteurope.de;regressions@leemhuis.info;1691516694;0c6296c6; X-HE-SMSGID: 1qTFeQ-0003sC-03 X-Spam-Status: No, score=1.4 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_BLOCKED, RCVD_IN_SBL_CSS,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.6 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 20.07.23 14:06, Mark Brown wrote: > On Thu, Jul 20, 2023 at 11:32:28AM +0100, Will Deacon wrote: >> On Tue, Jul 11, 2023 at 06:57:33PM +0100, Mark Brown wrote: > >>> Still investigating but I'm pretty convinced this is nothing to do with >>> your commit/series and is just common or garden memory corruption that >>> just happens to get tickled by your changes. Sorry for the noise. > >> Did you get to the bottom of this? If not, do you have a reliable way to >> reproduce the problem? I don't like the sound of memory corruption :( > > Not to the bottom of it, but getting there - I isolated the issue to > something in the unregistration path for thermal zones but didn't manage > to figure out exactly what. Hi Mark, just wondering did anything come out of this and is this still happening? I'm just wondering, as I still have this on my list of tracked regressions. Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) -- Everything you wanna know about Linux kernel regression tracking: https://linux-regtracking.leemhuis.info/about/#tldr If I did something stupid, please tell me, as explained on that page. #regzbot poke > There was some indication it might be a use > after free but I'm not convinced. > > I have a reliable way to reproduce this if you have a pine64plus, it > also shows up a lot on the Libretech Tritium but not quite so reliably > as pine64plus since Hugh's changes. Equally pine64plus was rock solid > until those so there's some timing/environment thing going on which > makes the issue manifest obviously, I expect you should be able to > trigger the issue by unregistering a thermal driver but the effects > might not be visible. > > There is a change on the list to make the Allwinner SoCs not trigger the > issue during boot (their thermal driver refuses to register if any one > zone fails but most of their SoCs have multiple thermal zones with only > one fully described) but it needs fixing either way.