From: George Dunlap <george.dunlap@eu.citrix.com>
To: xen-devel@lists.xen.org
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Ian Jackson <ian.jackson@citrix.com>,
Wei Liu <wei.liu2@citrix.com>,
George Dunlap <george.dunlap@citrix.com>
Subject: [PATCH 6/8] tools/xenalyze: Fix off-by-one in MAX_CPUS range checks
Date: Thu, 25 Feb 2016 14:49:01 +0000 [thread overview]
Message-ID: <1456411743-17741-7-git-send-email-george.dunlap@eu.citrix.com> (raw)
In-Reply-To: <1456411743-17741-1-git-send-email-george.dunlap@eu.citrix.com>
Skip action / throw error if cpu/vcpu >= MAX_CPUS rather than >.
Also add an assertion to vcpu_find, to make future errors of this kind
not out-of-bounds.
CID 1306871
CID 1306870
CID 1306869
CID 1306867
Signed-off-by: George Dunlap <george.dunlap@citrix.com>
---
CC: Ian Jackson <ian.jackson@citrix.com>
CC: Wei Liu <wei.liu2@citrix.com>
---
tools/xentrace/xenalyze.c | 17 ++++++++++++-----
1 file changed, 12 insertions(+), 5 deletions(-)
diff --git a/tools/xentrace/xenalyze.c b/tools/xentrace/xenalyze.c
index 249bebd..3e26a4c 100644
--- a/tools/xentrace/xenalyze.c
+++ b/tools/xentrace/xenalyze.c
@@ -6860,6 +6860,13 @@ struct vcpu_data * vcpu_find(int did, int vid)
struct domain_data *d;
struct vcpu_data *v;
+ /* "Graceful" handling of vid >= MAX_CPUS should be handled elsewhere */
+ if ( vid >= MAX_CPUS ) {
+ fprintf(stderr, "%s: vcpu %d exceeds MAX_CPUS %d!\n",
+ __func__, vid, MAX_CPUS);
+ error(ERR_ASSERT, NULL);
+ }
+
d = domain_find(did);
v = d->vcpu[vid];
@@ -7131,7 +7138,7 @@ void sched_runstate_process(struct pcpu_info *p)
}
}
- if(r->vcpu > MAX_CPUS)
+ if(r->vcpu >= MAX_CPUS)
{
fprintf(warn, "%s: vcpu %u > MAX_VCPUS %d!\n",
__func__, r->vcpu, MAX_CPUS);
@@ -7441,14 +7448,14 @@ void sched_switch_process(struct pcpu_info *p)
r->prev_dom, r->prev_vcpu,
r->next_dom, r->next_vcpu);
- if(r->prev_vcpu > MAX_CPUS)
+ if(r->prev_vcpu >= MAX_CPUS)
{
fprintf(warn, "%s: prev_vcpu %u > MAX_VCPUS %d!\n",
__func__, r->prev_vcpu, MAX_CPUS);
return;
}
- if(r->next_vcpu > MAX_CPUS)
+ if(r->next_vcpu >= MAX_CPUS)
{
fprintf(warn, "%s: next_vcpu %u > MAX_VCPUS %d!\n",
__func__, r->next_vcpu, MAX_CPUS);
@@ -8518,7 +8525,7 @@ off_t scan_for_new_pcpu(off_t offset) {
cd = (typeof(cd))rec.u.notsc.data;
- if ( cd->cpu > MAX_CPUS )
+ if ( cd->cpu >= MAX_CPUS )
{
fprintf(stderr, "%s: cpu %d exceeds MAX_CPU %d!\n",
__func__, cd->cpu, MAX_CPUS);
@@ -8738,7 +8745,7 @@ void process_cpu_change(struct pcpu_info *p) {
(unsigned long long)p->file_offset);
}
- if(r->cpu > MAX_CPUS)
+ if(r->cpu >= MAX_CPUS)
{
fprintf(stderr, "FATAL: cpu %d > MAX_CPUS %d.\n",
r->cpu, MAX_CPUS);
--
2.1.4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-02-25 14:49 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 14:48 [PATCH 0/8] Fixes to Coverity issues reported on xenalyze George Dunlap
2016-02-25 14:48 ` [PATCH 1/8] tools/xenalyze: Close symbol_file after reading it George Dunlap
2016-02-26 12:22 ` Ian Jackson
2016-02-29 16:11 ` Konrad Rzeszutek Wilk
2016-02-25 14:48 ` [PATCH 2/8] tools/xenalyze: Avoid redundant check George Dunlap
2016-02-26 12:23 ` Ian Jackson
2016-02-29 16:15 ` Konrad Rzeszutek Wilk
2016-02-25 14:48 ` [PATCH 3/8] tools/xenalyze: Handle fstat errors properly George Dunlap
2016-02-26 12:25 ` Ian Jackson
2016-03-03 12:28 ` George Dunlap
2016-02-25 14:48 ` [PATCH 4/8] tools/xenalyze: Mark unreachable code as unreachable George Dunlap
2016-02-25 15:03 ` Ian Campbell
2016-02-25 15:09 ` George Dunlap
2016-02-25 15:28 ` Ian Campbell
2016-02-25 15:43 ` George Dunlap
2016-02-25 15:52 ` Ian Campbell
2016-02-26 12:28 ` Ian Jackson
2016-02-25 14:49 ` [PATCH 5/8] tools/xenalyze: Fix check for error return value George Dunlap
2016-02-26 12:29 ` Ian Jackson
2016-02-29 16:16 ` Konrad Rzeszutek Wilk
2016-02-25 14:49 ` George Dunlap [this message]
2016-02-26 12:30 ` [PATCH 6/8] tools/xenalyze: Fix off-by-one in MAX_CPUS range checks Ian Jackson
2016-02-29 16:58 ` George Dunlap
2016-03-03 12:44 ` George Dunlap
2016-02-25 14:49 ` [PATCH 7/8] tools/xenalyze: Fix multiple instances of *HYPERCALL_MAX George Dunlap
2016-02-26 12:33 ` Ian Jackson
2016-02-29 17:29 ` George Dunlap
2016-03-01 13:36 ` Ian Jackson
2016-02-25 14:49 ` [PATCH 8/8] tools/xenalyze: Actually handle case where number of ipi vectors exceeds static max George Dunlap
2016-02-26 12:34 ` Ian Jackson
2016-02-29 16:16 ` Konrad Rzeszutek Wilk
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=1456411743-17741-7-git-send-email-george.dunlap@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=george.dunlap@citrix.com \
--cc=ian.jackson@citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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).