mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: Vladimir Murzin <vladimir.murzin@arm.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
	Nicolas Pitre <nicolas.pitre@linaro.org>,
	afzal mohammed <afzal.mohd.ma@gmail.com>,
	Laura Abbott <labbott@redhat.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: NOMMU: work around maybe-uninitialized warning
Date: Thu, 2 Nov 2017 13:07:34 +0000	[thread overview]
Message-ID: <20171102130734.GZ9463@n2100.armlinux.org.uk> (raw)
In-Reply-To: <681a1757-ddbe-c9a7-6945-fa72600cf172@arm.com>

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 <arnd@arndb.de>
> > ---
> > 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.

This isn't urgent.

-- 
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 8.8Mbps down 630kbps up
According to speedtest.net: 8.21Mbps down 510kbps up

  reply	other threads:[~2017-11-02 13:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-02  9:21 Arnd Bergmann
2017-11-02 12:25 ` Vladimir Murzin
2017-11-02 13:07   ` Russell King - ARM Linux [this message]
2017-11-02 13:11     ` Vladimir Murzin
2017-11-02 13:47       ` Russell King - ARM Linux

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171102130734.GZ9463@n2100.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=afzal.mohd.ma@gmail.com \
    --cc=arnd@arndb.de \
    --cc=labbott@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolas.pitre@linaro.org \
    --cc=vladimir.murzin@arm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®