qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Claudio Fontana <cfontana@suse.de>
To: Kevin Wolf <kwolf@redhat.com>
Cc: "Richard Henderson" <richard.henderson@linaro.org>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Markus Armbruster" <armbru@redhat.com>,
	qemu-devel@nongnu.org, dinechin@redhat.com,
	"Gerd Hoffmann" <kraxel@redhat.com>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH v3 2/3] module: add Error arguments to module_load_one and module_load_qom_one
Date: Wed, 21 Sep 2022 09:50:59 +0200	[thread overview]
Message-ID: <eda3f2ce-a828-8c84-60bd-684844eb25b6@suse.de> (raw)
In-Reply-To: <YynvR49aIK2AzbJ3@redhat.com>

On 9/20/22 18:50, Kevin Wolf wrote:
> Am 08.09.2022 um 19:36 hat Claudio Fontana geschrieben:
>> On 9/8/22 19:10, Claudio Fontana wrote:
>>> On 9/8/22 18:03, Richard Henderson wrote:
>>>> On 9/8/22 15:53, Claudio Fontana wrote:
>>>>> @@ -446,8 +447,13 @@ static int dmg_open(BlockDriverState *bs, QDict *options, int flags,
>>>>>           return -EINVAL;
>>>>>       }
>>>>>   
>>>>> -    block_module_load_one("dmg-bz2");
>>>>> -    block_module_load_one("dmg-lzfse");
>>>>> +    if (!block_module_load_one("dmg-bz2", &local_err) && local_err) {
>>>>> +        error_report_err(local_err);
>>>>> +    }
>>>>> +    local_err = NULL;
>>>>> +    if (!block_module_load_one("dmg-lzfse", &local_err) && local_err) {
>>>>> +        error_report_err(local_err);
>>>>> +    }
>>>>>   
>>>>>       s->n_chunks = 0;
>>>>>       s->offsets = s->lengths = s->sectors = s->sectorcounts = NULL;
>>>>
>>>> I wonder if these shouldn't fail hard if the modules don't exist?
>>>> Or at least pass back the error.
>>>>
>>>> Kevin?
>>
>> is "dmg-bz" _required_ for dmg open to work? I suspect if the dmg
>> image is not compressed, "dmg" can function even if the extra dmg-bz
>> module is not loaded right?
> 
> Indeed. The code seems to consider that the modules may not be present.
> The behaviour in these cases is questionable (it seems to silently leave
> the buffers as they are and return success), but the modules are clearly
> optional.
> 
>> I'd suspect we should then do:
>>
>> if (!block_module_load_one("dmg-bz2", &local_err)) {
>>   if (local_err) {
>>      error_report_err(local_err);
>>      return -EINVAL;
>>   }
>>   warn_report("dmg-bz2 is not present, dmg will skip bz2-compressed chunks */
>> }
>>
>> and same for dmg-lzfse...?
> 
> Actually, I think during initialisation, we should just pass NULL as
> errp and ignore any errors.

Hmm really? I'd think that if there is an actual error loading the module (module is installed, but the loading itself fails due to broken module, wrong permissions, I/O errors etc)
we would want to report that fact as it happens?

> 
> When a request would access a block that can't be uncompressed because
> of the missing module, that's where we can have a warn_report_once() and
> arguably should fail the I/O request.
> 
> Kevin
> 

That would mean, moving the

warn_report("dmg-bz2 is not present, dmg will skip bz2-compressed chunks")

to the uncompression code and change it to a warn_report_once() right?

Thanks,

Claudio


  parent reply	other threads:[~2022-09-21  7:54 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-08 14:53 [PATCH v3 0/3] improve error handling for module load Claudio Fontana
2022-09-08 14:53 ` [PATCH v3 1/3] module: removed unused function argument "mayfail" Claudio Fontana
2022-09-08 14:53 ` [PATCH v3 2/3] module: add Error arguments to module_load_one and module_load_qom_one Claudio Fontana
2022-09-08 16:03   ` Richard Henderson
2022-09-08 17:10     ` Claudio Fontana
2022-09-08 17:36       ` Claudio Fontana
2022-09-20 16:50         ` Kevin Wolf
2022-09-21  4:45           ` Markus Armbruster
2022-09-21 11:43             ` Kevin Wolf
2022-09-21 12:08               ` Markus Armbruster
2022-09-22 14:33                 ` Kevin Wolf
2022-09-22 15:09                   ` Markus Armbruster
2022-09-21  7:50           ` Claudio Fontana [this message]
2022-09-21 11:56             ` Kevin Wolf
2022-09-23 14:10               ` Claudio Fontana
2022-09-23 14:42                 ` Kevin Wolf
2022-09-23 14:46                   ` Claudio Fontana
2022-09-23 16:29                     ` Kevin Wolf
2022-09-23 22:23                       ` Claudio Fontana
2022-09-08 14:53 ` [PATCH v3 3/3] accel: abort if we fail to load the accelerator plugin Claudio Fontana
2022-09-08 16:03   ` Richard Henderson
  -- strict thread matches above, loose matches on Subject: below --
2022-09-08 15:00 [PATCH RESEND v3 0/3] improve error handling for module load Claudio Fontana
2022-09-08 15:00 ` [PATCH v3 2/3] module: add Error arguments to module_load_one and module_load_qom_one Claudio Fontana

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=eda3f2ce-a828-8c84-60bd-684844eb25b6@suse.de \
    --to=cfontana@suse.de \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=dinechin@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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 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).