From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: PXE directory listing incorrectly reported as "success"
Date: Wed, 27 Jan 2010 01:03:16 +0100 [thread overview]
Message-ID: <4B5F82C4.3030000@gmail.com> (raw)
In-Reply-To: <20100126170818.GA30854@thorin>
[-- Attachment #1: Type: text/plain, Size: 1054 bytes --]
Robert Millan wrote:
> Hi,
>
> It appears that directory listing isn't supported by TFTP protocol (so
> says our wiki).
>
> Our pxe.c implements grub_pxefs_dir() as a dummy stub that returns
> GRUB_ERR_NONE. This is obviously wrong, as it prevents the user from
> noticing that there was a problem, and silently reports an "empty"
> directory. Instead, it should call grub_error ().
>
> Unfortunately, kern/fs.c relies on grub_pxefs_dir() returning
> GRUB_ERR_NONE in order to consider probing to be succesful. If pxe
> returned an error, it wouldn't be considered a valid filesystem by
> the kernel.
>
> So I'm wondering, what would be a good solution to this?
What about return GRUB_ERR_UNSUPPORTED or a separate GRUB_ERR_FS_NO_DIR
which would be ignored by probing routines?
> We could add
> a proper probe() function and switch all filesystems to it, but only
> for the benefit of pxe it seems a bit overkill.
>
> Does someone have a better idea?
>
>
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 293 bytes --]
prev parent reply other threads:[~2010-01-27 0:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 17:08 PXE directory listing incorrectly reported as "success" Robert Millan
2010-01-26 18:03 ` Seth Goldberg
2010-01-27 0:03 ` 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=4B5F82C4.3030000@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.