[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CACRpkdbgMyYYm1v4BeFQBCz8jZVLE_0oZiKu5F3Rt6=ccfVnYA@mail.gmail.com>
Date: Tue, 9 Jul 2019 11:11:16 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Doug Berger <opendmb@...il.com>
Cc: Linux ARM <linux-arm-kernel@...ts.infradead.org>,
Russell King <linux@...linux.org.uk>,
Laura Abbott <labbott@...hat.com>,
Mike Rapoport <rppt@...ux.ibm.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Florian Fainelli <f.fainelli@...il.com>,
Rob Herring <robh@...nel.org>,
"Steven Rostedt (VMware)" <rostedt@...dmis.org>,
Peng Fan <peng.fan@....com>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] ARM: mm: only adjust sections of valid mm structures
On Thu, Jun 27, 2019 at 11:33 PM Doug Berger <opendmb@...il.com> wrote:
> A timing hazard exists when an early fork/exec thread begins
> exiting and sets its mm pointer to NULL while a separate core
> tries to update the section information.
>
> This commit ensures that the mm pointer is not NULL before
> setting its section parameters. The arguments provided by
> commit 11ce4b33aedc ("ARM: 8672/1: mm: remove tasklist locking
> from update_sections_early()") are equally valid for not
> requiring grabbing the task_lock around this check.
>
> Fixes: 08925c2f124f ("ARM: 8464/1: Update all mm structures with section adjustments")
> Signed-off-by: Doug Berger <opendmb@...il.com>
Cc: stable@...r.kernel.org ?
I'm not smart enough to say whether it is the right solution, but
I also want to test this on some boards I have. I suspect this
may be part of the problem I have with mounting root on a USB
stick on some early mpcore machines, so I might come back with
a Tested-by.
Yours,
Linus Walleij
Powered by blists - more mailing lists