From: Kevin Wolf <kwolf@redhat.com>
To: Claudio Fontana <cfontana@suse.de>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"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é" <f4bug@amsat.org>
Subject: Re: [PATCH v9 0/5] improve error handling for module load
Date: Thu, 27 Oct 2022 20:34:11 +0200 [thread overview]
Message-ID: <Y1rPI2sXcxjbVIbd@redhat.com> (raw)
In-Reply-To: <b68f4730-be61-b635-057e-270f3f74f63b@suse.de>
Am 27.10.2022 um 16:52 hat Claudio Fontana geschrieben:
> A ping on this one, is there anything more that needs to be urgently
> addressed before it can be queued for inclusion? This is currently
> creating problems for upstream kubevirt, due to the error handling not
> properly reporting permissions errors on module file access.
What is the right tree to take this one?
get_maintainers.pl doesn't show anything for module.[ch], which might be
why nobody feels responsible for merging this.
Kevin
next prev parent reply other threads:[~2022-10-27 19:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 9:30 [PATCH v9 0/5] improve error handling for module load Claudio Fontana
2022-09-29 9:30 ` [PATCH v9 1/5] module: removed unused function argument "mayfail" Claudio Fontana
2022-09-29 9:30 ` [PATCH v9 2/5] module: rename module_load_one to module_load Claudio Fontana
2022-09-29 9:30 ` [PATCH v9 3/5] module: add Error arguments to module_load and module_load_qom Claudio Fontana
2022-09-29 9:30 ` [PATCH v9 4/5] dmg: warn when opening dmg images containing blocks of unknown type Claudio Fontana
2022-09-29 9:30 ` [PATCH v9 5/5] accel: abort if we fail to load the accelerator plugin Claudio Fontana
2022-10-21 8:24 ` [PATCH v9 0/5] improve error handling for module load Claudio Fontana
2022-10-27 14:52 ` Claudio Fontana
2022-10-27 18:34 ` Kevin Wolf [this message]
2022-11-04 9:05 ` Claudio Fontana
2022-11-04 11:43 ` Peter Maydell
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=Y1rPI2sXcxjbVIbd@redhat.com \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=cfontana@suse.de \
--cc=dinechin@redhat.com \
--cc=f4bug@amsat.org \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@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 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.