From: Roger Pau Monne <roger.pau@citrix.com>
To: xen-devel@lists.xenproject.org
Cc: Henry.Wang@arm.com, "Roger Pau Monne" <roger.pau@citrix.com>,
"Jan Beulich" <jbeulich@suse.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"George Dunlap" <george.dunlap@citrix.com>,
"Wei Liu" <wl@xen.org>, "Edwin Török" <edvin.torok@citrix.com>
Subject: [PATCH for-4.17?] x86/paging: return -EINVAL for paging domctls for dying domains
Date: Tue, 8 Nov 2022 12:38:50 +0100 [thread overview]
Message-ID: <20221108113850.61619-1-roger.pau@citrix.com> (raw)
Like on the Arm side, return -EINVAL when attempting to do a p2m
operation on dying domains.
The current logic returns 0 and leaves the domctl parameter
uninitialized for any parameter fetching operations (like the
GET_ALLOCATION operation), which is not helpful from a toolstack point
of view, because there's no indication that the data hasn't been
fetched.
Reported-by: Edwin Török <edvin.torok@citrix.com>
Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
---
I'm adding the for-4.17 tag because I think this is a backport
candidate to older Xen versions also.
---
xen/arch/x86/mm/paging.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/xen/arch/x86/mm/paging.c b/xen/arch/x86/mm/paging.c
index 3a355eee9c..3e7be07e86 100644
--- a/xen/arch/x86/mm/paging.c
+++ b/xen/arch/x86/mm/paging.c
@@ -694,9 +694,10 @@ int paging_domctl(struct domain *d, struct xen_domctl_shadow_op *sc,
if ( unlikely(d->is_dying) )
{
- gdprintk(XENLOG_INFO, "Ignoring paging op on dying domain %u\n",
+ gdprintk(XENLOG_INFO,
+ "Tried to do a paging domctl op on dying domain %u\n",
d->domain_id);
- return 0;
+ return -EINVAL;
}
if ( unlikely(d->vcpu == NULL) || unlikely(d->vcpu[0] == NULL) )
--
2.37.3
next reply other threads:[~2022-11-08 11:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 11:38 Roger Pau Monne [this message]
2022-11-08 16:14 ` [PATCH for-4.17?] x86/paging: return -EINVAL for paging domctls for dying domains Jan Beulich
2022-11-08 16:43 ` Roger Pau Monné
2022-11-08 17:03 ` Jan Beulich
2022-11-08 17:15 ` Roger Pau Monné
2022-11-09 7:48 ` Jan Beulich
2022-11-09 9:45 ` Edwin Torok
2022-11-09 9:58 ` Jan Beulich
2022-11-09 10:11 ` Roger Pau Monné
2022-11-09 10:23 ` Jan Beulich
2022-11-09 11:36 ` Roger Pau Monné
2022-11-09 12:02 ` Jan Beulich
2022-11-09 13:22 ` Roger Pau Monné
2022-11-10 9:03 ` Jan Beulich
2022-11-08 17:30 ` Edwin Torok
2022-11-09 16:11 ` Andrew Cooper
2022-11-10 9:02 ` Jan Beulich
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=20221108113850.61619-1-roger.pau@citrix.com \
--to=roger.pau@citrix.com \
--cc=Henry.Wang@arm.com \
--cc=andrew.cooper3@citrix.com \
--cc=edvin.torok@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=jbeulich@suse.com \
--cc=wl@xen.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 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.