From: "Vesa Jääskeläinen" <chaac@nic.fi>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: /kern/file.c BUG
Date: Thu, 24 Jan 2008 20:08:46 +0200 [thread overview]
Message-ID: <4798D42E.7030506@nic.fi> (raw)
In-Reply-To: <20080124000544.GB32503@thorin>
Robert Millan wrote:
> On Wed, Jan 23, 2008 at 11:00:57PM +0000, Oleg Strikov wrote:
>> Incorrect behavior of grub_file_open () function in e.g. loop context:
>>
>> char *file_names[] =
>> {
>> "(hd0,1)/file1", //file do not exist
>> "(hd0,1)/file2" //file exist
>> };
>> grub_file_t file;
>> int i;
>> for (i = 0; i < 2; i++)
>> {
>> file = grub_file_open (file_names[i]);
>> if (file) {...}
>> }
>>
>> There, we should get positive return in the second case (i == 1), but
>> grub_file_open() returns 0.
>>
>> Using gdb i've found that this problem connected with incorrect errno check
>> in /kern/file.c
>>
>> Let's look:
>>
>>> grub_file_t
>>> grub_file_open (const char *name)
>>> {
>>> grub_device_t device;
>>> grub_file_t file = 0;
>>> char *device_name;
>>> char *file_name;
>>> device_name = grub_file_get_device_name (name);
>>> if (grub_errno)
>>> return 0;
>> But, we DO NOT set grub_errno to 0 at the begining of the function, thats
>> why next loop round it always returns 0
>
> Fixed, thank you.
Now you broke it ;)
Previous behavior was working correctly. You have to handle errorcodes
at some point and that means when error is handled it is zeroed (or
GRUB_ERR_NONE). So code is in callee where that loop was.
next prev parent reply other threads:[~2008-01-24 18:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-23 23:00 /kern/file.c BUG Oleg Strikov
2008-01-24 0:05 ` Robert Millan
2008-01-24 18:08 ` Vesa Jääskeläinen [this message]
2008-01-24 18:34 ` Pavel Roskin
2008-01-24 21:19 ` Yoshinori K. Okuji
2008-01-24 22:09 ` Marco Gerards
2008-01-24 23:00 ` Robert Millan
2008-01-24 23:27 ` Robert Millan
2008-01-25 8:47 ` Marco Gerards
2008-01-25 8:45 ` Marco Gerards
2008-01-25 8:50 ` Marco Gerards
2008-01-25 23:57 ` Robert Millan
2008-01-26 12:04 ` Marco Gerards
2008-01-26 17:05 ` Robert Millan
-- strict thread matches above, loose matches on Subject: below --
2008-01-24 21:43 Oleg Strikov
2008-01-25 3:22 ` Pavel Roskin
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=4798D42E.7030506@nic.fi \
--to=chaac@nic.fi \
--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.