Received: by 10.223.164.221 with SMTP id h29csp2118143wrb; Thu, 2 Nov 2017 06:12:30 -0700 (PDT) X-Google-Smtp-Source: ABhQp+ThDnrVFtQ5CjsPw8dDiiSIBaoSxaPBAFb2pbYIiR5Ku9q0GpP9tA50QRK23qJ0gYgTmBKw X-Received: by 10.99.4.129 with SMTP id 123mr3507028pge.20.1509628349924; Thu, 02 Nov 2017 06:12:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1509628349; cv=none; d=google.com; s=arc-20160816; b=sVy/0oE4T1CntPBKesorqfTn3GBw8kEK0S6g4oP0DgLa8yjpZRacw/ESIwEdFQl/k/ aCR49W8s0E2q2Ik3GebgdohV0abSLH9b7Q939vnT6Or7PbpoPqV5LgeJy6EwU/mhq/Y3 Seb8EwrM1Ej8M33mD7a0fcJ6NGRWF8aX2cRTe7wuzEB4287UsOcWlveFFI7c18Ta9mOs lB6MOxAWfdH52FK2oI3zgYV8yc7WMSOFcgQTtB997DOQatnBKEsSJ5eCTskrmFqoLBdX VYqbccFDEpp9V05+o2tE4sVAp3M1dxohxm7a8rgPCtHdjZ0pHZEGrr3HC8BUdRxVGnkh jjQA== 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 :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:arc-authentication-results; bh=aC1m439Gymz3kBcm5fFJODCK8rnwyVN1oy33sCxgrls=; b=m7QW0UZzvs8wnZzS3U8beC7Ceuu+uq3zdcrOXO1aGZsyQf7AJDI4w98uyQqAFTX2sl rdSMWW4LxJlWIU9F59YxxRVYLIaaXMm8dODxy25YlRfbo3bAIJJZ49R2ZRXyzsGehj/M bdtOywMV1v4L2Fk34905TY+X0CopJgF5/lMAW/LuVW+Rw1Zf3wj5GgevxmK5yqL1QdO+ cfhLw/G4JD87m5OoJpksdrRdVzSRbzq1ngIExXftBwUPmv1C3/S2NlcrlYs2ZHfZxKhT ++pnHMBTbG/rczdBghybn1oOfYA8Lvu1E1J//0MLHMbiYTs82fv5PYNzD8Gp/eHFL3tU La8g== 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 i10si3643243pgc.293.2017.11.02.06.12.15; Thu, 02 Nov 2017 06:12:29 -0700 (PDT) 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 S1755468AbdKBNL3 (ORCPT + 96 others); Thu, 2 Nov 2017 09:11:29 -0400 Received: from foss.arm.com ([217.140.101.70]:59860 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751974AbdKBNL0 (ORCPT ); Thu, 2 Nov 2017 09:11:26 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id E36701529; Thu, 2 Nov 2017 06:11:25 -0700 (PDT) Received: from [10.1.79.67] (unknown [10.1.79.67]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 8DAB63F483; Thu, 2 Nov 2017 06:11:24 -0700 (PDT) Subject: Re: [PATCH] ARM: NOMMU: work around maybe-uninitialized warning To: Russell King - ARM Linux Cc: Arnd Bergmann , Nicolas Pitre , afzal mohammed , Laura Abbott , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org References: <20171102092155.737712-1-arnd@arndb.de> <681a1757-ddbe-c9a7-6945-fa72600cf172@arm.com> <20171102130734.GZ9463@n2100.armlinux.org.uk> From: Vladimir Murzin Message-ID: Date: Thu, 2 Nov 2017 13:11:23 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <20171102130734.GZ9463@n2100.armlinux.org.uk> Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 02/11/17 13:07, Russell King - ARM Linux wrote: > On Thu, Nov 02, 2017 at 12:25:47PM +0000, Vladimir Murzin wrote: >> On 02/11/17 09:21, Arnd Bergmann wrote: >>> The reworked MPU code produces a new warning in some configurations, >>> presumably starting with the code move after the compiler now makes >>> different inlining decisions: >>> >>> arch/arm/mm/pmsa-v7.c: In function 'adjust_lowmem_bounds_mpu': >>> arch/arm/mm/pmsa-v7.c:310:5: error: 'specified_mem_size' may be used uninitialized in this function [-Werror=maybe-uninitialized] >>> >>> This appears to be harmless, as we know that there is always at >>> least one memblock, and the only way this could get triggered is >>> if the for_each_memblock() loop was never entered. >>> >>> I could not come up with a better workaround than initializing >>> the specified_mem_size to zero, but at least that is the value >>> that the variable would have in the hypothetical case of no >>> memblocks. >>> >>> Fixes: 877ec119dbbf ("ARM: 8706/1: NOMMU: Move out MPU setup in separate module") >>> Signed-off-by: Arnd Bergmann >>> --- >>> Vladimir, if this looks good to you, can you forward it to Russell's >>> patch tracker, or otherwise suggest a different fix? >> >> Accepted as patch 8719/1. Not sure if Russell will pick it up or not... anyway, >> thanks for the patch! > > I'd prefer not to at this stage. Same things that apply that I said > in the "ARM: early_printk: use printascii() rather than printch()" > thread - I need to ensure that what I have is stable before 4.14 is > released, so I'm not accepting anything further unless it is _really_ > urgent. Yes, I saw that thread, it is why that "not sure" thing. > > This isn't urgent. > Should I resubmit after -rc1 or you'll apply it directly from patch tracker? Thanks Vladimir From 1582959861321303749@xxx Thu Nov 02 13:09:23 +0000 2017 X-GM-THRID: 1582945654361281415 X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread