From: Dan Carpenter <dan.carpenter@oracle.com>
To: Jeremy Fitzhardinge <jeremy@xensource.com>
Cc: Tang Liang <liang.tang@oracle.com>,
virtualization@lists.linux-foundation.org
Subject: memory corruption in HYPERVISOR_physdev_op()
Date: Fri, 14 Sep 2012 14:24:27 +0300 [thread overview]
Message-ID: <20120914112427.GA1454@elgon.mountain> (raw)
Hi Jeremy,
My static analyzer complains about potential memory corruption in
HYPERVISOR_physdev_op()
arch/x86/include/asm/xen/hypercall.h
389 static inline int
390 HYPERVISOR_physdev_op(int cmd, void *arg)
391 {
392 int rc = _hypercall2(int, physdev_op, cmd, arg);
393 if (unlikely(rc == -ENOSYS)) {
394 struct physdev_op op;
395 op.cmd = cmd;
396 memcpy(&op.u, arg, sizeof(op.u));
397 rc = _hypercall1(int, physdev_op_compat, &op);
398 memcpy(arg, &op.u, sizeof(op.u));
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Some of the arg buffers are not as large as sizeof(op.u) which is either
12 or 16 depending on the size of longs in struct physdev_apic.
399 }
400 return rc;
401 }
One example of this is in xen_initdom_restore_msi_irqs().
arch/x86/pci/xen.c
337 struct physdev_pci_device restore_ext;
338
339 restore_ext.seg = pci_domain_nr(dev->bus);
340 restore_ext.bus = dev->bus->number;
341 restore_ext.devfn = dev->devfn;
342 ret = HYPERVISOR_physdev_op(PHYSDEVOP_restore_msi_ext,
343 &restore_ext);
^^^^^^^^^^^^
There are only 4 bytes here.
344 if (ret == -ENOSYS)
^^^^^^^^^^^^^^
If we hit this condition, we have corrupted some memory.
345 pci_seg_supported = false;
regards,
dan carpenter
next reply other threads:[~2012-09-14 11:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-14 11:24 Dan Carpenter [this message]
2012-10-15 10:27 ` memory corruption in HYPERVISOR_physdev_op() Ian Campbell
[not found] ` <1350296868.18058.24.camel@zakaz.uk.xensource.com>
2012-10-15 10:48 ` [Xen-devel] " Jan Beulich
2012-10-15 10:58 ` Ian Campbell
2012-10-15 12:46 ` Jan Beulich
2012-10-16 9:07 ` Jan Beulich
2012-10-16 9:13 ` 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=20120914112427.GA1454@elgon.mountain \
--to=dan.carpenter@oracle.com \
--cc=jeremy@xensource.com \
--cc=liang.tang@oracle.com \
--cc=virtualization@lists.linux-foundation.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).