linux-kernel - Re: Linux-next-20191106 : arm64: Internal error: Oops: 96000007

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CACRpkdY5JObOobs7VW043QYGd_xufwnQDBJseKp+_QWv4kdzaQ@mail.gmail.com>
Date:   Thu, 7 Nov 2019 09:00:25 +0100
From:   Linus Walleij <linus.walleij@...aro.org>
To:     Mark Brown <broonie@...nel.org>
Cc:     Robin Murphy <robin.murphy@....com>,
        Naresh Kamboju <naresh.kamboju@...aro.org>,
        Catalin Marinas <catalin.marinas@....com>,
        Will Deacon <will@...nel.org>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        Arnd Bergmann <arnd@...db.de>,
        open list <linux-kernel@...r.kernel.org>,
        lkft-triage@...ts.linaro.org, John Stultz <john.stultz@...aro.org>,
        Linux-Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: Linux-next-20191106 : arm64: Internal error: Oops: 96000007

On Wed, Nov 6, 2019 at 5:17 PM Mark Brown <broonie@...nel.org> wrote:
> On Wed, Nov 06, 2019 at 04:07:52PM +0000, Robin Murphy wrote:
>
> > FWIW this smells like a builtin driver had its of_device_id table marked
> > __init, leaving drv->of_match_table as a dangling pointer to freed memory by
> > this point.
>
> Indeed, in fact I sent a fix for this to Linus Walleij yesterday having
> seen the relevant build warning when testing -next.  Someone already
> reported that it fixed the boot issues.  Hopefully Linus will pick it up
> soon :/

Yeah picked it up and pushed out now. I wish I'd been quicker with
it but the patch spot activity has been high. (Bad signal-to-noise
ratio on the mailing lists.)

I wonder if it's worth to look at the static checkers like checkpatch
to warn for this?

There is always a bit of delicate balance between just fixing some
weird one-off problems and making sure they never happen again.

Yours,
Linus Walleij