Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp235256ybl; Wed, 4 Dec 2019 01:44:23 -0800 (PST) X-Google-Smtp-Source: APXvYqx4fdLbVHp7j9ksQDbELT6vupgFgwyyyXGXgi5GynfeXCFTdGMqEqGWBUFI6mFptNvZIJn2 X-Received: by 2002:aca:ecd3:: with SMTP id k202mr1785026oih.71.1575452663205; Wed, 04 Dec 2019 01:44:23 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1575452663; cv=none; d=google.com; s=arc-20160816; b=O7PjwDV35RxvmsSY/FxsFihRgoz1l4wPMJAM57QO6tsFYeEYN+Zxwqbc9WrIPF1EvS 9nsAuewu0eEQrSIMXqaWuETT4SRDFEujcYufYjgQMUwDk589vFygSijBVRtaOTq8ibAS x5KUKGNhEc4yrTr1P730Pa/eNyMnt5F0W/xLNEKgmhhHZB4uh0gNbupw0xqFjWz1hFRV Eg5PKqJnp2Oz9Mce7nFdkVyYtx64vGOMBd1zCJYrhenZpFa+RdnbNmrC6obNp3fIdgxA V7tPXoNI/cbGcbBz/bp6DhmiMSUeox9h14FmXNldYCpc8MG2X8gCdYY3/J2BDEDW91nS 0LVw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=zYSDf9IST2S5nc6Er5YufivxXdWqyKugIJZudAafSUs=; b=bKUUBxh8V84zmAzXs8Ua5Pujt23UyM/llADImUv9FAvdLaGgj03QglbQoSjmfVHXer jlFZvknfba9ivwNh+9cms2JBdaFHhgsEjyfeIV02mEiV3h/OiR/+g/nXGINUQntQ4nuj xiOR0Dgv1MRvo+QikIuUyi5u9RkzCXJA7Ftq7eDjPjwBzL2tnMV1fW0dpG4lQ3FcrrEs ak9V5wZx3ecmvDWLvWPbd6qW+z0HsYamWpqhj0/qTCLh93hQSchvbEO2tEuxf9HiPSXk GSyA0lmEVTRdGsm2vpvrUcrW/TbXAwyoB9Da+9zCizX7cJczz3AcI/SUdUF/ZgSWnCin DBqg== ARC-Authentication-Results: i=1; mx.google.com; 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 q10si2918135otn.53.2019.12.04.01.44.09; Wed, 04 Dec 2019 01:44:23 -0800 (PST) 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; 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 S1727136AbfLDJmW (ORCPT + 99 others); Wed, 4 Dec 2019 04:42:22 -0500 Received: from foss.arm.com ([217.140.110.172]:53398 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726632AbfLDJmV (ORCPT ); Wed, 4 Dec 2019 04:42:21 -0500 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 447BD1FB; Wed, 4 Dec 2019 01:42:21 -0800 (PST) Received: from e107158-lin.cambridge.arm.com (e107158-lin.cambridge.arm.com [10.1.195.21]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id E50183F52E; Wed, 4 Dec 2019 01:42:19 -0800 (PST) Date: Wed, 4 Dec 2019 09:42:17 +0000 From: Qais Yousef To: Vincent Guittot Cc: John Stultz , Quentin Perret , Peter Zijlstra , Dietmar Eggemann , Juri Lelli , Valentin Schneider , Patrick Bellasi , Ingo Molnar , lkml Subject: Re: Null pointer crash at find_idlest_group on db845c w/ linus/master Message-ID: <20191204094216.u7yld5r3zelp22lf@e107158-lin.cambridge.arm.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20171215 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 12/04/19 09:06, Vincent Guittot wrote: > Hi John, > > On Tue, 3 Dec 2019 at 20:15, John Stultz wrote: > > > > With today's linus/master on db845c running android, I'm able to > > fairly easily reproduce the following crash. I've not had a chance to > > bisect it yet, but I'm suspecting its connected to Vincent's recent > > rework. > > Does the crash happen randomly or after a specific action ? > I have a db845 so I can try to reproduce it locally. Isn't there a chance we use local_sgs without initializing it in that function? AFAICS we define local_sgs on the stack but not always could be populated with the right values. I can't see tmp_sgs being used in the function too. Could this cause the/a problem? 8377 struct sg_lb_stats local_sgs, tmp_sgs; . . . 8399 if (local_group) { 8400 sgs = &local_sgs; 8401 local = group; 8402 } else { 8403 sgs = &tmp_sgs; 8404 } 8405 8406 update_sg_wakeup_stats(sd, group, sgs, p); Cheers -- Qais Youef