From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Bernhard Walle" <bwalle@suse.de>, "Ingo Molnar" <mingo@elte.hu>
Cc: x86@kernel.org, vgoyal@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] e820_update_range(): Allow specifying ULLONG_MAX
Date: Tue, 24 Jun 2008 13:21:44 -0700 [thread overview]
Message-ID: <86802c440806241321g6c5cd64eoe504d6029de6fe5a@mail.gmail.com> (raw)
In-Reply-To: <86802c440806241301x4d124335h2888de9e915208ae@mail.gmail.com>
On Tue, Jun 24, 2008 at 1:01 PM, Yinghai Lu <yhlu.kernel@gmail.com> wrote:
> On Tue, Jun 24, 2008 at 7:35 AM, Bernhard Walle <bwalle@suse.de> wrote:
>> Allow the specifying of ULLONG_MAX to limit the whole E820 map from the
>> specified start to the end. Without the patch, there would be integer
>> overflows.
>>
>>
>> Signed-off-by: Bernhard Walle <bwalle@suse.de>
>> ---
>> arch/x86/kernel/e820.c | 11 +++++++++--
>> 1 files changed, 9 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/x86/kernel/e820.c b/arch/x86/kernel/e820.c
>> index e466073..7d1109b 100644
>> --- a/arch/x86/kernel/e820.c
>> +++ b/arch/x86/kernel/e820.c
>> @@ -397,6 +397,9 @@ int __init copy_e820_map(struct e820entry *biosmap, int nr_map)
>> return __copy_e820_map(biosmap, nr_map);
>> }
>>
>> +/*
>> + * Pass size == ULLONG_MAX to update until the end.
>> + */
>> u64 __init e820_update_range(u64 start, u64 size, unsigned old_type,
>> unsigned new_type)
>> {
>> @@ -412,14 +415,18 @@ u64 __init e820_update_range(u64 start, u64 size, unsigned old_type,
>> continue;
>> /* totally covered? */
>> if (ei->addr >= start &&
>> - (ei->addr + ei->size) <= (start + size)) {
>> + (((ei->addr + ei->size) <= (start + size)) ||
>> + (size == ULLONG_MAX))) {
>> ei->type = new_type;
>> real_updated_size += ei->size;
>> continue;
>> }
>> /* partially covered */
>> final_start = max(start, ei->addr);
>> - final_end = min(start + size, ei->addr + ei->size);
>> + if (size == ULLONG_MAX)
>> + final_end = ei->addr + ei->size;
>> + else
>> + final_end = min(start + size, ei->addr + ei->size);
>> if (final_start >= final_end)
>> continue;
>> ei->size -= final_end - final_start;
>> --
>
>
> it seems we should let the caller to use
> e820_update_range(start, ULLONG_MAX - size,....)
>
> so you don't need to touch this func.
or add sanitary check before using size in this func like
if (size > ULLONG_MAX - start)
size = ULLONG_MAX - start;
e820_remove_range need to the same thing
YH
next prev parent reply other threads:[~2008-06-24 20:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-24 14:35 Limit E820 map when specifying mem parameter Bernhard Walle
2008-06-24 14:35 ` [PATCH 1/3] e820_update_range(): Strip size of original region Bernhard Walle
2008-06-24 19:57 ` Yinghai Lu
2008-06-25 12:04 ` Bernhard Walle
2008-06-24 14:35 ` [PATCH 2/3] e820_update_range(): Allow specifying ULLONG_MAX Bernhard Walle
2008-06-24 20:01 ` Yinghai Lu
2008-06-24 20:21 ` Yinghai Lu [this message]
2008-06-25 12:05 ` Bernhard Walle
2008-06-25 15:44 ` Ingo Molnar
2008-06-24 14:35 ` [PATCH 3/3] Limit E820 map when a user-defined memory map is specified Bernhard Walle
2008-06-24 20:03 ` Yinghai Lu
2008-06-25 12:02 Limit E820 map when specifying mem parameter Bernhard Walle
2008-06-25 12:02 ` [PATCH 2/3] e820_update_range(): Allow specifying ULLONG_MAX Bernhard Walle
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=86802c440806241321g6c5cd64eoe504d6029de6fe5a@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=bwalle@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=vgoyal@redhat.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
all inboxes | Powered by JetHome®