From: "H. Peter Anvin" <hpa@zytor.com>
To: Juergen Gross <jgross@suse.com>,
linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org,
x86@kernel.org, linux-doc@vger.kernel.org
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
corbet@lwn.net, boris.ostrovsky@oracle.com
Subject: Re: PLEASE REVERT URGENTLY: Re: [PATCH v5 2/3] x86/boot: add acpi rsdp address to setup_header
Date: Fri, 9 Nov 2018 16:38:15 -0800 [thread overview]
Message-ID: <7cede814-a441-05b6-10aa-5713da8ad843@zytor.com> (raw)
In-Reply-To: <f7c78ee7-b548-7f04-24da-7321b6c64c97@zytor.com>
One more aspect on this patchset: when CONFIG_ACPI_TABLE_UPGRADE was
inroduced, it was seen as a security problem and disabled by default
(unlike for device tree, where feeding entries from the boot loader is
standard operating procedure.)
Thus functionally makes that possible to bypass that prohibition. Are we
giving up that battle, or should this also be conditionalized and
default to off (presumably with Xen requiring it)?
-hpa
next prev parent reply other threads:[~2018-11-10 0:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 6:14 [PATCH v5 0/3] x86: make rsdp address accessible via boot params Juergen Gross
2018-10-10 6:14 ` [PATCH v5 1/3] x86/xen: fix boot loader version reported for pvh guests Juergen Gross
2018-10-10 6:14 ` [PATCH v5 2/3] x86/boot: add acpi rsdp address to setup_header Juergen Gross
2018-11-09 22:23 ` PLEASE REVERT URGENTLY: " H. Peter Anvin
2018-11-10 0:38 ` H. Peter Anvin [this message]
2018-11-10 6:26 ` Juergen Gross
2018-11-10 6:32 ` H. Peter Anvin
2018-11-10 7:02 ` Juergen Gross
2018-11-10 7:16 ` H. Peter Anvin
2018-11-10 9:03 ` Juergen Gross
2018-11-11 18:49 ` H. Peter Anvin
2018-11-19 16:48 ` Konrad Rzeszutek Wilk
2018-11-10 15:22 ` Juergen Gross
2018-11-11 23:58 ` hpa
2018-10-10 6:14 ` [PATCH v5 3/3] x86/acpi: take rsdp address for boot params if available Juergen Gross
2018-10-10 6:23 ` [PATCH v5 0/3] x86: make rsdp address accessible via boot params Ingo Molnar
2018-10-10 6:39 ` Juergen Gross
2018-10-10 7:19 ` Ingo Molnar
2018-10-10 7:28 ` Juergen Gross
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=7cede814-a441-05b6-10aa-5713da8ad843@zytor.com \
--to=hpa@zytor.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=jgross@suse.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.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
all inboxes | Powered by JetHome®