From: Mark Brown <broonie@kernel•org>
To: Robin Murphy <robin.murphy@arm•com>
Cc: Naresh Kamboju <naresh.kamboju@linaro•org>,
Russell King - ARM Linux <linux@armlinux•org.uk>,
catalin.marinas@arm•com, will@kernel•org,
linux-arm-kernel@lists•infradead.org,
Stephen Rothwell <sfr@canb•auug.org.au>,
Arnd Bergmann <arnd@arndb•de>,
open list <linux-kernel@vger•kernel.org>,
lkft-triage@lists•linaro.org,
John Stultz <john.stultz@linaro•org>,
Linux-Next Mailing List <linux-next@vger•kernel.org>,
Linus Walleij <linus.walleij@linaro•org>
Subject: Re: Linux-next-20191106 : arm64: Internal error: Oops: 96000007
Date: Wed, 6 Nov 2019 16:17:05 +0000 [thread overview]
Message-ID: <20191106161705.GA11849@sirena.co.uk> (raw)
In-Reply-To: <bfced8c8-c64f-982e-8797-d48b5ec65291@arm.com>
[-- Attachment #1: Type: text/plain, Size: 454 bytes --]
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 :/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-11-06 16:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 15:56 Linux-next-20191106 : arm64: Internal error: Oops: 96000007 Naresh Kamboju
2019-11-06 16:07 ` Robin Murphy
2019-11-06 16:16 ` Mark Rutland
2019-11-06 16:17 ` Mark Brown [this message]
2019-11-07 8:00 ` Linus Walleij
2019-11-07 11:45 ` Mark Brown
2019-11-07 11:59 ` Ben Dooks
2019-11-06 17:19 ` Russell King - ARM Linux admin
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=20191106161705.GA11849@sirena.co.uk \
--to=broonie@kernel$(echo .)org \
--cc=arnd@arndb$(echo .)de \
--cc=catalin.marinas@arm$(echo .)com \
--cc=john.stultz@linaro$(echo .)org \
--cc=linus.walleij@linaro$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux@armlinux$(echo .)org.uk \
--cc=lkft-triage@lists$(echo .)linaro.org \
--cc=naresh.kamboju@linaro$(echo .)org \
--cc=robin.murphy@arm$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=will@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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