linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: Laura Abbott <labbott@redhat.com>, matt@codeblueprint.co.uk
Cc: waiman.long@hpe.com, ard.biesheuvel@linaro.org,
	Borislav Petkov <bp@alien8.de>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	tytso@mit.edu, Arnd Bergmann <arnd@arndb.de>,
	Greg KH <gregkh@linuxfoundation.org>,
	scott.norton@hpe.com, doug.hatch@hpe.com,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	x86@kernel.org, linux-efi@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [REGRESSION][v4.9.y][v4.10.y] x86/efi: Only map RAM into EFI page tables if in mixed-mode
Date: Fri, 3 Feb 2017 09:16:48 -0500	[thread overview]
Message-ID: <f8b36e38-c1f6-82f8-0ed9-0c934ace44ac@canonical.com> (raw)
In-Reply-To: <d5f1ba6b-06ed-b5b0-1b0e-58d5f385f7c2@redhat.com>

On 02/02/2017 03:36 PM, Laura Abbott wrote:
> On 02/02/2017 12:17 PM, Joseph Salisbury wrote:
>> Hi Matt,
>>
>> A kernel bug report was opened against Ubuntu [0].  After a kernel
>> bisect, it was found that reverting the following commit resolved this bug:
>>
>> commit 1297667083d5442aafe3e337b9413bf02b114edb
>> Author: Matt Fleming <matt@codeblueprint.co.uk>
>> Date:   Mon Sep 19 13:09:09 2016 +0100
>>
>>     x86/efi: Only map RAM into EFI page tables if in mixed-mode
>>
>>
>> The regression was introduced as of v4.8-rc8.  It also still affects
>> current mainline.
>>
>> I was hoping to get your feedback, since you are the patch author.  Do
>> you think gathering any additional data will help diagnose this issue,
>> or would it be best to submit a revert request?
>>
>>
>> Thanks,
>>
>> Joe
>>
>> [0] http://pad.lv/1659340
>>
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe stable" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
> You might try https://marc.info/?l=linux-kernel&m=148553171703761
> which fixed https://bugzilla.redhat.com/show_bug.cgi?id=1384238
>
> Thanks,
> Laura

This patch resolves the bug for multiple users.  Thanks again for the
pointer, Laura and Ard!


Joe

  parent reply	other threads:[~2017-02-03 14:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-02 20:17 [REGRESSION][v4.9.y][v4.10.y] x86/efi: Only map RAM into EFI page tables if in mixed-mode Joseph Salisbury
2017-02-02 20:34 ` Ard Biesheuvel
2017-02-02 20:36 ` Laura Abbott
2017-02-02 20:49   ` Joseph Salisbury
2017-02-03 14:16   ` Joseph Salisbury [this message]
2017-02-03 16:35     ` Linus Torvalds

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=f8b36e38-c1f6-82f8-0ed9-0c934ace44ac@canonical.com \
    --to=joseph.salisbury@canonical.com \
    --cc=ard.biesheuvel@linaro.org \
    --cc=arnd@arndb.de \
    --cc=bp@alien8.de \
    --cc=doug.hatch@hpe.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hpa@zytor.com \
    --cc=labbott@redhat.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt@codeblueprint.co.uk \
    --cc=mingo@redhat.com \
    --cc=scott.norton@hpe.com \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=tytso@mit.edu \
    --cc=waiman.long@hpe.com \
    --cc=x86@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
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;
as well as URLs for NNTP newsgroup(s).