From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: ELF check: GRUB_ERR_BAD_FILE_TYPE vs. GRUB_ERR_BAD_OS
Date: Sat, 25 Jul 2015 13:52:09 +0200 [thread overview]
Message-ID: <55B37869.1050507@gmail.com> (raw)
In-Reply-To: <20150724215059.5e06dace@opensuse.site>
[-- Attachment #1: Type: text/plain, Size: 597 bytes --]
On 24.07.2015 20:50, Andrei Borzenkov wrote:
> There are two places using GRUB_ERR_BAD_FILE_TYPE and other are using
> GRUB_ERR_BAD_OS when EFL class check fails. I am not sure about exact
> semantics of either but probably they should be the same?
>
BAD_FILE_TYPE is only for errors like EISDIR and ENODIR. BAD_OS should
be used for invalid ELF contents or BAD_MODULE if elf code is primarily
meant to load GRUB-shipped ELFs.
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 213 bytes --]
prev parent reply other threads:[~2015-07-25 11:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-24 18:50 ELF check: GRUB_ERR_BAD_FILE_TYPE vs. GRUB_ERR_BAD_OS Andrei Borzenkov
2015-07-25 11:52 ` Vladimir 'φ-coder/phcoder' Serbinenko [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=55B37869.1050507@gmail.com \
--to=phcoder@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.