From: Chen Gong <gong.chen@linux.intel.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: "bp@alien8.de" <bp@alien8.de>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH 1/2 V2] ACPI/APEI: Add parameter check before error injection
Date: Wed, 22 May 2013 02:10:29 -0400 [thread overview]
Message-ID: <20130522061029.GA25406@gchen.bj.intel.com> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F2DA69843@ORSMSX106.amr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 2367 bytes --]
On Tue, May 21, 2013 at 08:19:16PM +0000, Luck, Tony wrote:
> Date: Tue, 21 May 2013 20:19:16 +0000
> From: "Luck, Tony" <tony.luck@intel.com>
> To: Chen Gong <gong.chen@linux.intel.com>, "bp@alien8.de" <bp@alien8.de>
> CC: "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
> Subject: RE: [PATCH 1/2 V2] ACPI/APEI: Add parameter check before error
> injection
>
> + /* ensure param1/param2 existed */
> + if (!(param_extension || acpi5))
> + goto inject;
> +
> + /* ensure injection is memory related */
> + if (type & ACPI5_VENDOR_BIT) {
> + if (vendor_flags != SETWA_FLAGS_MEM)
> + goto inject;
> + } else if (!(type & MEM_ERROR_MASK))
> + goto inject;
>
> Maybe a comment before all these three goto blocks saying why we are jumping
> around. Perhaps:
>
> /* We need extra sanity checks for memory errors. Other types leap directly to injection */
>
Thanks, this comment is great.
> +
> + /*
> + * When error injection type is memory related, param2 is the address
> + * mask of param1. This mask is used to ensure that the final address
> + * (param1 & param2) is meaningful. If param2 has a *weird* style
> + * like 0xf0f0f0f0f0f0f0f0, it means the injection address can be
> + * anywhere around param1, and that must be forbidden. In that reason,
> + * PAGE_MASK is employed to avoid injection address discontinuous.
> + * If one finds a special case not to satisfy this requirement, please
> + * fix it.
> + */
> + pfn = PFN_DOWN(param1 & param2);
> + if (!page_is_ram(pfn) || ((param2 & PAGE_MASK) != PAGE_MASK))
> + return -EINVAL;
>
> This has too much comment (rare!) and is still too complicated. Split the tests apart?
Your comment is great to me. Boris ever mentioned that
"(param2 & PAGE_MASK) != PAGE_MASK)" is not usual, most of situations are
like "(param2 & PAGE_MASK) != param2). So he wants here I can give a clear
explanation for it. Maybe I can move my explanation into patch description.
>
> /*
> * Disallow crazy address masks that give BIOS leeway to pick injection address
> * almost anywhere. Insist on page or better granularity
> */
> if ((param2 & PAGE_MASK) != PAGE_MASK)
> return -EINVAL;
>
> /* make sure target address is normal memory */
> pfn = PFN_DOWN(param1 & param2);
> if (!page_is_ram(pfn))
> return -EINVAL;
>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-05-22 6:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 7:20 Parameter check for EINJ error injection - V2 Chen Gong
2013-05-20 7:20 ` [PATCH 1/2 V2] ACPI/APEI: Add parameter check before error injection Chen Gong
2013-05-21 20:19 ` Luck, Tony
2013-05-22 6:10 ` Chen Gong [this message]
2013-05-22 10:33 ` Borislav Petkov
2013-05-20 7:20 ` [PATCH 2/2 V2] ACPI/APEI: Update einj documentation for param1/param2 Chen Gong
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=20130522061029.GA25406@gchen.bj.intel.com \
--to=gong.chen@linux.intel.com \
--cc=bp@alien8.de \
--cc=linux-acpi@vger.kernel.org \
--cc=tony.luck@intel.com \
/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).