From: Jan Beulich <jbeulich@suse.com>
To: Jason Andryuk <jason.andryuk@amd.com>
Cc: xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
Juergen Gross <jgross@suse.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>
Subject: Re: [PATCH v2 1/3] xen/events: Cleanup find_virq() return codes
Date: Tue, 26 Aug 2025 09:22:10 +0200 [thread overview]
Message-ID: <de9005bf-c858-4e7e-bea8-33e5ea2424fc@suse.com> (raw)
In-Reply-To: <20250826005517.41547-2-jason.andryuk@amd.com>
On 26.08.2025 02:55, Jason Andryuk wrote:
> rc is overwritten by the evtchn_status hypercall in each iteration, so
> the return value will be whatever the last iteration is.
Which may even be a false "success". Especially for that it feels like ...
> Change to an
> explicit -ENOENT for an un-found virq and return 0 on a successful
> match.
>
> Signed-off-by: Jason Andryuk <jason.andryuk@amd.com>
... this also wants a Fixes: tag and perhaps a Cc: to stable@.
> --- a/drivers/xen/events/events_base.c
> +++ b/drivers/xen/events/events_base.c
> @@ -1318,7 +1318,7 @@ static int find_virq(unsigned int virq, unsigned int cpu, evtchn_port_t *evtchn)
> {
> struct evtchn_status status;
> evtchn_port_t port;
> - int rc = -ENOENT;
> + int rc;
Maybe best to also move this into the more narrow scope (loop body)?
Either way:
Reviewed-by: Jan Beulich <jbeulich@suse.com>
> memset(&status, 0, sizeof(status));
Having this outside of the loop is a little odd, too: It makes assumptions
on the behavior of the hypervisor (like not altering the structure upon
error). Yet likely not something to deal with right here.
Jan
next prev parent reply other threads:[~2025-08-26 7:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-26 0:55 [PATCH v2 0/3] xen/events: Fix Global and Domain VIRQ tracking Jason Andryuk
2025-08-26 0:55 ` [PATCH v2 1/3] xen/events: Cleanup find_virq() return codes Jason Andryuk
2025-08-26 7:22 ` Jan Beulich [this message]
2025-08-26 15:03 ` Jason Andryuk
2025-08-27 15:16 ` Jürgen Groß
2025-08-26 0:55 ` [PATCH v2 2/3] xen/events: Return -EEXIST for bound VIRQs Jason Andryuk
2025-08-27 15:21 ` Jürgen Groß
2025-08-27 22:11 ` Jason Andryuk
2025-08-26 0:55 ` [PATCH v2 3/3] xen/events: Update virq_to_irq on migration Jason Andryuk
2025-08-27 15:28 ` Jürgen Groß
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=de9005bf-c858-4e7e-bea8-33e5ea2424fc@suse.com \
--to=jbeulich@suse.com \
--cc=jason.andryuk@amd.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleksandr_tyshchenko@epam.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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
all inboxes | Powered by JetHome®