From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: matthieu castet <castet.matthieu@free.fr>
Cc: linux-acpi@vger.kernel.org, Pavel Machek <pavel@ucw.cz>,
Len Brown <lenb@kernel.org>
Subject: Re: [PATCH] check that acpi_wakeup_address is below 1MB
Date: Thu, 7 Feb 2008 00:10:48 +0100 [thread overview]
Message-ID: <200802070010.48992.rjw@sisk.pl> (raw)
In-Reply-To: <47AA38EF.6030307@free.fr>
On Wednesday, 6 of February 2008, matthieu castet wrote:
> Hi,
Hi,
> this patch had a check that the memory allocated is in the first 1MB.
> The check is similar to the one in smp_alloc_memory.
>
>
> Signed-off-by: "Matthieu CASTET <castet.matthieu@free.fr>"
Please don't attach patches if possible. It's easier to comment them if they
are in the message body.
> diff --git a/arch/x86/kernel/acpi/sleep.c b/arch/x86/kernel/acpi/sleep.c
> index 6bc815c..65ab23c 100644
> --- a/arch/x86/kernel/acpi/sleep.c
> +++ b/arch/x86/kernel/acpi/sleep.c
> @@ -65,6 +65,10 @@ void __init acpi_reserve_bootmem(void)
> acpi_wakeup_address = (unsigned long)alloc_bootmem_low(PAGE_SIZE*2);
> if (!acpi_wakeup_address)
> printk(KERN_ERR "ACPI: Cannot allocate lowmem, S3 disabled.\n");
> +
> + /* check if we are in first 1MB of memory */
> + if (__pa(acpi_wakeup_address) >= 1024*1024-PAGE_SIZE*2)
> + BUG();
I don't like this.
First, you should use BUG_ON(something) rather that "if (something) BUG();".
Second, and more importantly, it's enough to put "acpi_wakeup_address = 0"
to disable the feature without crashing the kernel.
Of course, I'd add an error message describing what's wrong to that.
> }
Thanks,
Rafael
--
"Premature optimization is the root of all evil." - Donald Knuth
prev parent reply other threads:[~2008-02-06 23:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-06 22:47 [PATCH] check that acpi_wakeup_address is below 1MB matthieu castet
2008-02-06 22:56 ` Ingo Molnar
2008-02-06 23:10 ` Rafael J. Wysocki [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=200802070010.48992.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=castet.matthieu@free.fr \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=pavel@ucw.cz \
/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