qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: David Hildenbrand <david@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Igor Mammedov" <imammedo@redhat.com>,
	"Thiner Logoer" <logoerthiner1@163.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Daniel P . Berrangé" <berrange@redhat.com>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Elena Ufimtseva" <elena.ufimtseva@oracle.com>,
	"Jagannathan Raman" <jag.raman@oracle.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"Ani Sinha" <anisinha@redhat.com>,
	"Xiao Guangrong" <xiaoguangrong.eric@gmail.com>,
	"Daniel Henrique Barboza" <danielhb413@gmail.com>,
	"Greg Kurz" <groug@kaod.org>, "Eric Blake" <eblake@redhat.com>,
	"Markus Armbruster" <armbru@redhat.com>,
	"Eduardo Habkost" <eduardo@habkost.net>
Subject: Re: [PATCH v3 07/11] softmmu/physmem: Never return directories from file_ram_open()
Date: Wed, 23 Aug 2023 16:22:16 -0400	[thread overview]
Message-ID: <ZOZqeBInVdNpGZEo@x1n> (raw)
In-Reply-To: <20230823153412.832081-8-david@redhat.com>

On Wed, Aug 23, 2023 at 05:34:07PM +0200, David Hildenbrand wrote:
> open() does not fail on directories when opening them readonly (O_RDONLY).
> 
> Currently, we succeed opening such directories and fail later during
> mmap(), resulting in a misleading error message.
> 
> $ ./qemu-system-x86_64 \
>     -object memory-backend-file,id=ram0,mem-path=tmp,readonly=true,size=1g
>  qemu-system-x86_64: unable to map backing store for guest RAM: No such device
> 
> To identify directories and handle them accordingly in file_ram_open()
> also when readonly=true was specified, detect if we just opened a directory
> using fstat() instead. Then, fail file_ram_open() right away, similarly
> to how we now fail if the file does not exist and we want to open the
> file readonly.
> 
> With this change, we get a nicer error message:
>  qemu-system-x86_64: can't open backing store tmp for guest RAM: Is a directory
> 
> Note that the only memory-backend-file will end up calling
> memory_region_init_ram_from_file() -> qemu_ram_alloc_from_file() ->
> file_ram_open().
> 
> Reported-by: Thiner Logoer <logoerthiner1@163.com>
> Signed-off-by: David Hildenbrand <david@redhat.com>

Reviewed-by: Peter Xu <peterx@redhat.com>

-- 
Peter Xu



  reply	other threads:[~2023-08-23 20:22 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-23 15:34 [PATCH v3 00/11] memory-backend-file related improvements and VM templating support David Hildenbrand
2023-08-23 15:34 ` [PATCH v3 01/11] nvdimm: Reject writing label data to ROM instead of crashing QEMU David Hildenbrand
2023-08-23 15:34 ` [PATCH v3 02/11] softmmu/physmem: Distinguish between file access mode and mmap protection David Hildenbrand
2023-08-23 20:21   ` Peter Xu
2023-08-23 15:34 ` [PATCH v3 03/11] backends/hostmem-file: Add "rom" property to support VM templating with R/O files David Hildenbrand
2023-09-01 12:50   ` Markus Armbruster
2023-08-23 15:34 ` [PATCH v3 04/11] softmmu/physmem: Remap with proper protection in qemu_ram_remap() David Hildenbrand
2023-08-23 20:21   ` Peter Xu
2023-08-29 11:18   ` Philippe Mathieu-Daudé
2023-08-23 15:34 ` [PATCH v3 05/11] softmmu/physmem: Bail out early in ram_block_discard_range() with readonly files David Hildenbrand
2023-08-23 20:21   ` Peter Xu
2023-08-23 15:34 ` [PATCH v3 06/11] softmmu/physmem: Fail creation of new files in file_ram_open() with readonly=true David Hildenbrand
2023-08-23 20:22   ` Peter Xu
2023-08-23 15:34 ` [PATCH v3 07/11] softmmu/physmem: Never return directories from file_ram_open() David Hildenbrand
2023-08-23 20:22   ` Peter Xu [this message]
2023-08-23 15:34 ` [PATCH v3 08/11] docs: Don't mention "-mem-path" in multi-process.rst David Hildenbrand
2023-08-23 15:34 ` [PATCH v3 09/11] docs: Start documenting VM templating David Hildenbrand
2023-08-29 11:25   ` Philippe Mathieu-Daudé
2023-08-23 15:34 ` [PATCH v3 10/11] softmmu/physmem: Hint that "readonly=on, rom=off" exists when opening file R/W for private mapping fails David Hildenbrand
2023-08-23 15:34 ` [PATCH v3 11/11] machine: Improve error message when using default RAM backend id David Hildenbrand
2023-08-25  6:57   ` ThinerLogoer
2023-08-25  7:36     ` [PATCH " David Hildenbrand
2023-08-25  9:10       ` Markus Armbruster
2023-08-25  9:13         ` David Hildenbrand
2023-08-25  9:56           ` Markus Armbruster
2023-08-25  9:59             ` David Hildenbrand
2023-08-25 10:10               ` David Hildenbrand
2023-08-29 11:29                 ` Philippe Mathieu-Daudé
2023-09-01 12:52                 ` Markus Armbruster
2023-08-29  8:31   ` Mario Casquero

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=ZOZqeBInVdNpGZEo@x1n \
    --to=peterx@redhat.com \
    --cc=anisinha@redhat.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=danielhb413@gmail.com \
    --cc=david@redhat.com \
    --cc=eblake@redhat.com \
    --cc=eduardo@habkost.net \
    --cc=elena.ufimtseva@oracle.com \
    --cc=groug@kaod.org \
    --cc=imammedo@redhat.com \
    --cc=jag.raman@oracle.com \
    --cc=logoerthiner1@163.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=xiaoguangrong.eric@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).