Linux-Next Archive on lore.kernel.org
 help / color / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Mark Brown <broonie@kernel.org>
Cc: Robin Murphy <robin.murphy@arm.com>,
	Naresh Kamboju <naresh.kamboju@linaro.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>,
	Linux ARM <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>
Subject: Re: Linux-next-20191106 : arm64: Internal error: Oops: 96000007
Date: Thu, 7 Nov 2019 09:00:25 +0100
Message-ID: <CACRpkdY5JObOobs7VW043QYGd_xufwnQDBJseKp+_QWv4kdzaQ@mail.gmail.com> (raw)
In-Reply-To: <20191106161705.GA11849@sirena.co.uk>

On Wed, Nov 6, 2019 at 5:17 PM Mark Brown <broonie@kernel.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

  reply index

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-06 15:56 Naresh Kamboju
2019-11-06 16:07 ` Robin Murphy
2019-11-06 16:16   ` Mark Rutland
2019-11-06 16:17   ` Mark Brown
2019-11-07  8:00     ` Linus Walleij [this message]
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 publically 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=CACRpkdY5JObOobs7VW043QYGd_xufwnQDBJseKp+_QWv4kdzaQ@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=john.stultz@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=robin.murphy@arm.com \
    --cc=sfr@canb.auug.org.au \
    --cc=will@kernel.org \
    /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

Linux-Next Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-next/0 linux-next/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-next linux-next/ https://lore.kernel.org/linux-next \
		linux-next@vger.kernel.org
	public-inbox-index linux-next

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-next


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git