From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-next PATCH] arm64: fix kernel crash with 48-bit VA and 64KB granule
Date: Wed, 6 Jan 2016 09:51:07 +0000 [thread overview]
Message-ID: <20160106095107.GA16580@arm.com> (raw)
In-Reply-To: <20160106085929.GB7879@arm.org>
Dennis,
On Wed, Jan 06, 2016 at 04:59:30PM +0800, Dennis Chen wrote:
> On Wed, Jan 06, 2016 at 09:54:42AM +0100, Ard Biesheuvel wrote:
> > On 6 January 2016 at 09:52, Dennis Chen <dennis.chen@arm.com> wrote:
> > > On Wed, Jan 06, 2016 at 08:42:20AM +0100, Ard Biesheuvel wrote:
> > >> On 6 January 2016 at 08:38, Dennis Chen <dennis.chen@arm.com> wrote:
> > >> > Well, if the build system changes the link order, it can't make sure it will break something
> > >> > unexpectedly, needless to say the pgd_cache_init here at all.
> > >>
> > >> That is no excuse to introduce yet another failure mode.
> > >>
> > >> > Do you think the kernel
> > >> > will change its currently link order policy? If the answer is yes, what's the benefit?
> > >> >
> > >>
> > >> It does not matter what I think. You seem to think that the link order
> > >> is set in stone, so it is you who should argue why that is a
> > >> reasonable assumption.
> > >>
> > > OK, If you think the link order is volatile, how can you guarantee the arm_enable_runtime_services with early_initcall
> > > always work in a volatile link order environment?
> > >
> >
> > By not relying on other early_initcalls
> >
> You're limiting the scope of the link order
Please stop this mindless bickering. It's a waste of everybody's time and
we have a kernel to test.
Will
next prev parent reply other threads:[~2016-01-06 9:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 2:18 [linux-next PATCH] arm64: fix kernel crash with 48-bit VA and 64KB granule Dennis Chen
2016-01-05 7:36 ` Ard Biesheuvel
2016-01-05 8:35 ` Dennis Chen
2016-01-05 8:38 ` Ard Biesheuvel
2016-01-05 8:40 ` Dennis Chen
2016-01-05 9:56 ` Catalin Marinas
2016-01-06 6:14 ` Dennis Chen
2016-01-06 7:13 ` Ard Biesheuvel
2016-01-06 7:38 ` Dennis Chen
2016-01-06 7:42 ` Ard Biesheuvel
2016-01-06 8:52 ` Dennis Chen
2016-01-06 8:54 ` Ard Biesheuvel
2016-01-06 8:59 ` Dennis Chen
2016-01-06 9:51 ` Will Deacon [this message]
2016-01-05 12:31 ` Will Deacon
2016-01-05 12:47 ` Ard Biesheuvel
2016-01-05 15:44 ` Will Deacon
2016-01-06 2:55 ` Dennis Chen
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=20160106095107.GA16580@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.