public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64/efi: remove spurious WARN_ON for !4K kernels
Date: Thu, 23 Jun 2016 14:17:38 +0100	[thread overview]
Message-ID: <20160623131738.GH8836@leverpostej> (raw)
In-Reply-To: <20160617211601.GN2658@codeblueprint.co.uk>

On Fri, Jun 17, 2016 at 10:16:01PM +0100, Matt Fleming wrote:
> On Fri, 03 Jun, at 11:00:40AM, Will Deacon wrote:
> > 
> > Mark, Jeremy?
> > 
> > I've kept this patch marked as unread, but it's not clear to me (a) how
> > urgent it is (b) what tree it should go through and (c) whether it's the
> > right thing to do!
> 
> Ping? Anyone got an update here?

Sorry, I'd been meaning to come back to this.

As Ard noted, there are serious cases that this detects which we cannot
handle, and a WARN_ON for those is appropriate.

For the alignment of regions as required for permissions, I believe we
need clarification in the spec, and in the mean time I think we should
keep the WARN_ON.

To accurately report problems with differing attributes within a
(kernel) page, we need more comprehensive checks on the EFI memory map,
and potentially in some cases where we handle things dynamically at run
time. I haven't had the chance to delve into those yet.

So I guess for the timebeing this should stay as a WARN_ON, even if in
some cases it is spurious.

Thanks,
Mark.

      reply	other threads:[~2016-06-23 13:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-25 15:11 [PATCH] arm64/efi: remove spurious WARN_ON for !4K kernels Mark Rutland
2016-05-25 15:23 ` Ard Biesheuvel
2016-05-25 16:12   ` Mark Rutland
2016-05-25 18:23     ` Ard Biesheuvel
2016-05-26 10:56       ` Mark Rutland
2016-06-03 15:50         ` Ard Biesheuvel
2016-05-25 15:31 ` Catalin Marinas
2016-05-25 15:38 ` Jeremy Linton
2016-05-30 21:12 ` Matt Fleming
2016-06-03 10:00   ` Will Deacon
2016-06-17 21:16     ` Matt Fleming
2016-06-23 13:17       ` Mark Rutland [this message]

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=20160623131738.GH8836@leverpostej \
    --to=mark.rutland@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox