public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gerd Hoffmann" <kraxel@redhat.com>
To: Pedro Falcato <pedro.falcato@gmail.com>
Cc: Laszlo Ersek <lersek@redhat.com>,
	devel@edk2.groups.io,  Ard Biesheuvel <ardb+tianocore@kernel.org>,
	Jiewen Yao <jiewen.yao@intel.com>,
	 Jordan Justen <jordan.l.justen@intel.com>
Subject: Re: [edk2-devel] [PATCH] OvmfPkg/VirtioFsDxe: tolerate opening an abs. pathname rel. to a reg. file
Date: Mon, 23 Oct 2023 11:17:38 +0200	[thread overview]
Message-ID: <fc3cyfuxzfhuiiufsgy7bjyrjrxnuombp47x6ae47eeb6mt4tp@ul5ualq7kp2p> (raw)
In-Reply-To: <CAKbZUD3XOxvpQwxrbeH9utFi_0PdVKEGY4Gch9uPX_gczO7dzA@mail.gmail.com>

  Hi,
 
> To the RH folks, what's the easiest way of testing shim booting *with this bug*?

I've just passed the host ESP to the guest using virtiofs, libvirt xml
for that looks like this:

    <filesystem type='mount' accessmode='passthrough'>
      <driver type='virtiofs'/>
      <source dir='/boot/efi'/>
      <target dir='/boot/efi'/>
      <boot order='1'/>
      <address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/>
    </filesystem>

Then boot with an empty varstore and watch shim fail to read
EFI/$distro/BOOTX64.CSV

For the ext4 filesystem driver you probably need an ESP in ext4
filesystem format to test this.

take care,
  Gerd



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#109906): https://edk2.groups.io/g/devel/message/109906
Mute This Topic: https://groups.io/mt/102044004/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



      reply	other threads:[~2023-10-23  9:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-18 17:24 [edk2-devel] [PATCH] OvmfPkg/VirtioFsDxe: tolerate opening an abs. pathname rel. to a reg. file Laszlo Ersek
2023-10-19  6:28 ` Gerd Hoffmann
2023-10-19 13:04   ` Laszlo Ersek
2023-10-19 13:50 ` Pedro Falcato
2023-10-19 14:16   ` Laszlo Ersek
2023-10-20 22:11     ` Pedro Falcato
2023-10-23  9:17       ` Gerd Hoffmann [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-list 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=fc3cyfuxzfhuiiufsgy7bjyrjrxnuombp47x6ae47eeb6mt4tp@ul5ualq7kp2p \
    --to=devel@edk2.groups.io \
    /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