From: Andrei Borzenkov <arvidjaar@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Dell Dimension 8300 reboots when grub2 cbfs module is loaded
Date: Tue, 3 Nov 2015 20:19:22 +0300 [thread overview]
Message-ID: <5638EC9A.1060702@gmail.com> (raw)
In-Reply-To: <5638EB78.6010501@gmail.com>
03.11.2015 20:14, Andrei Borzenkov пишет:
> 03.11.2015 20:10, Vladimir 'phcoder' Serbinenko пишет:
>> Which platform is it? i386-pc, i386-efi or x86_64-efi? The behavior is
>> actually will defined, just different between cpu modes
>
> i386-pc
>
BTW here are specs from Dell site
Intel® Pentium® 4 microprocessor (2.4, 2.6, 2.8, 3.0,
3.2, and 3.4 for 800 FSB, and 2.4, 2.66, 2.8, and 3.06
for 533 FSB)
4GB max memory
Intel 875P chipset
>> Le 3 nov. 2015 6:08 PM, "Andrei Borzenkov" <arvidjaar@gmail.com> a
>> écrit :
>>
>>> 03.11.2015 19:28, Vladimir 'phcoder' Serbinenko пишет:
>>>
>>>> The code itself looks good but I'd like more details. Reading
>>>> 0xffffffff
>>>> shouldn't cause reboot. Why does it?
>>>>
>>>
>>> That I do not know nor do I have access to system in question myself. I
>>> sent user patch that modified validate_header to do each comparison as
>>> individual statement and did line by line debug print (fortunately it
>>> was
>>> possible to connect serial port and capture output) and the last line
>>> printed was immediately before the very first
>>>
>>> head->magic == grub_cpu_to_be32_compile_time (CBFS_HEADER_MAGIC
>>>
>>> I suppose reading *one* byte from 0xffffffff should not cause issues but
>>> here we are reading 4 bytes which are beyond 0xffffffff. Who knows what
>>> memory controller in this system does in this case.
>>>
>>> Le 1 nov. 2015 3:53 PM, "Andrei Borzenkov" <arvidjaar@gmail.com> a
>>> écrit :
>>>>
>>>> I was debugging problem reported by user on Dell Dimension 8300 - it
>>>>> rebooted when doing "ls -l". It turned out, the problem was
>>>>> triggered by
>>>>> loading cbfs which probed for header. System has 2GB memory, and
>>>>> attempt
>>>>> to
>>>>> read from address 0xffffffff caused instant reboot. 0xffffffff was
>>>>> returned
>>>>> by read from non-existing address 0xfffffffc.
>>>>>
>>>>> The proof of concept patch below avoids it, but I wonder what the
>>>>> proper
>>>>> fix is.
>>>>>
>>>>> diff --git a/grub-core/fs/cbfs.c b/grub-core/fs/cbfs.c
>>>>> index a34eb88..a5a2fde 100644
>>>>> --- a/grub-core/fs/cbfs.c
>>>>> +++ b/grub-core/fs/cbfs.c
>>>>> @@ -344,8 +344,9 @@ init_cbfsdisk (void)
>>>>>
>>>>> ptr = *(grub_uint32_t *) 0xfffffffc;
>>>>> head = (struct cbfs_header *) (grub_addr_t) ptr;
>>>>> + grub_dprintf ("cbfs", "head=%p\n", head);
>>>>>
>>>>> - if (!validate_head (head))
>>>>> + if (0xffffffff - ptr < sizeof (*head) || !validate_head (head))
>>>>> return;
>>>>>
>>>>> cbfsdisk_size = ALIGN_UP (grub_be_to_cpu32 (head->romsize),
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Grub-devel mailing list
>>>>> Grub-devel@gnu.org
>>>>> https://lists.gnu.org/mailman/listinfo/grub-devel
>>>>>
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Grub-devel mailing list
>>>> Grub-devel@gnu.org
>>>> https://lists.gnu.org/mailman/listinfo/grub-devel
>>>>
>>>>
>>>
>>> _______________________________________________
>>> Grub-devel mailing list
>>> Grub-devel@gnu.org
>>> https://lists.gnu.org/mailman/listinfo/grub-devel
>>>
>>
>>
>>
>> _______________________________________________
>> Grub-devel mailing list
>> Grub-devel@gnu.org
>> https://lists.gnu.org/mailman/listinfo/grub-devel
>>
>
next prev parent reply other threads:[~2015-11-03 17:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-01 14:53 Dell Dimension 8300 reboots when grub2 cbfs module is loaded Andrei Borzenkov
2015-11-03 16:12 ` [coreboot] " Martin Roth
2015-11-03 16:28 ` Vladimir 'phcoder' Serbinenko
2015-11-03 17:08 ` Andrei Borzenkov
2015-11-03 17:10 ` Vladimir 'phcoder' Serbinenko
2015-11-03 17:14 ` Andrei Borzenkov
2015-11-03 17:19 ` Andrei Borzenkov [this message]
2015-11-03 17:46 ` [coreboot] " Aaron Durbin
2015-11-03 18:05 ` Vladimir 'phcoder' Serbinenko
2015-11-03 21:41 ` Nico Huber
2015-11-04 11:35 ` Andrei Borzenkov
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=5638EC9A.1060702@gmail.com \
--to=arvidjaar@gmail.com \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.