From: Juergen Gross <jgross@suse.com>
To: Ingo Molnar <mingo@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
x86@kernel.org, lenb@kernel.org, rafael.j.wysocki@intel.com,
tglx@linutronix.de, mingo@redhat.com
Subject: Re: [PATCH] x86/acpi: check rsdp address received via bootparams to be valid
Date: Tue, 13 Feb 2018 17:48:43 +0100 [thread overview]
Message-ID: <1d6083f2-0a3e-2f3a-7089-426f81e8af93@suse.com> (raw)
In-Reply-To: <20180213163244.j2zuxyhs4kbfhwgj@gmail.com>
On 13/02/18 17:32, Ingo Molnar wrote:
>
> * Juergen Gross <jgross@suse.com> wrote:
>
>> So what about the following:
>>
>> From version 0x020e on (current version without my patches is 0x020d)
>> the boot loader will write its supported version or'ed with 0x8000 into
>> the same version field. So we can be sure any added fields are filled
>> with real data or the information has been evaluated by the boot loader,
>> if the returned version included that field. If the boot loader finds
>> the kernel supports a version < 0x020e it won't return its supported
>> version.
>
> This seems like a usable workaround to me, as long as everyone involved
> agrees with it.
Okay, thanks for the feedback.
I'll go that route.
> I've removed the patches for the time being.
Seems a sensible thing to do.
Juergen
next prev parent reply other threads:[~2018-02-13 16:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 13:57 [PATCH] x86/acpi: check rsdp address received via bootparams to be valid Juergen Gross
2018-01-16 15:46 ` Ingo Molnar
2018-01-16 15:56 ` Juergen Gross
2018-01-16 16:35 ` Ingo Molnar
2018-01-17 12:28 ` Juergen Gross
2018-01-17 15:34 ` Ingo Molnar
2018-01-17 18:12 ` Juergen Gross
2018-02-13 16:32 ` Ingo Molnar
2018-02-13 16:48 ` Juergen Gross [this message]
2018-01-17 11:49 ` Rafael J. Wysocki
2018-01-17 12:20 ` 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=1d6083f2-0a3e-2f3a-7089-426f81e8af93@suse.com \
--to=jgross@suse.com \
--cc=hpa@zytor.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=rafael.j.wysocki@intel.com \
--cc=tglx@linutronix.de \
--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