1. 10 9月, 2015 1 次提交
  2. 24 6月, 2015 2 次提交
  3. 02 6月, 2015 4 次提交
    • J
      xen/pt: unknown PCI config space fields should be read-only · c25bbf15
      Jan Beulich 提交于
      ... by default. Add a per-device "permissive" mode similar to pciback's
      to allow restoring previous behavior (and hence break security again,
      i.e. should be used only for trusted guests).
      
      This is part of XSA-131.
      Signed-off-by: NJan Beulich <jbeulich@suse.com>
      Acked-by: NStefano Stabellini <stefano.stabellini@eu.citrix.com>
      Reviewed-by: Anthony PERARD <anthony.perard@citrix.com>)
      c25bbf15
    • J
      xen/pt: mark reserved bits in PCI config space fields · 0ad3393a
      Jan Beulich 提交于
      The adjustments are solely to make the subsequent patches work right
      (and hence make the patch set consistent), namely if permissive mode
      (introduced by the last patch) gets used (as both reserved registers
      and reserved fields must be similarly protected from guest access in
      default mode, but the guest should be allowed access to them in
      permissive mode).
      
      This is a preparatory patch for XSA-131.
      Signed-off-by: NJan Beulich <jbeulich@suse.com>
      0ad3393a
    • J
      xen/MSI-X: limit error messages · b38ec5ee
      Jan Beulich 提交于
      Limit error messages resulting from bad guest behavior to avoid allowing
      the guest to cause the control domain's disk to fill.
      
      The first message in pci_msix_write() can simply be deleted, as this
      is indeed bad guest behavior, but such out of bounds writes don't
      really need to be logged.
      
      The second one is more problematic, as there guest behavior may only
      appear to be wrong: For one, the old logic didn't take the mask-all bit
      into account. And then this shouldn't depend on host device state (i.e.
      the host may have masked the entry without the guest having done so).
      Plus these writes shouldn't be dropped even when an entry is unmasked.
      Instead, if they can't be made take effect right away, they should take
      effect on the next unmasking or enabling operation - the specification
      explicitly describes such caching behavior. Until we can validly drop
      the message (implementing such caching/latching behavior), issue the
      message just once per MSI-X table entry.
      
      Note that the log message in pci_msix_read() similar to the one being
      removed here is not an issue: "addr" being of unsigned type, and the
      maximum size of the MSI-X table being 32k, entry_nr simply can't be
      negative and hence the conditonal guarding issuing of the message will
      never be true.
      
      This is XSA-130.
      Signed-off-by: NJan Beulich <jbeulich@suse.com>
      Reviewed-by: NStefano Stabellini <stefano.stabellini@eu.citrix.com>
      b38ec5ee
    • J
      xen: properly gate host writes of modified PCI CFG contents · 5c83b2f5
      Jan Beulich 提交于
      The old logic didn't work as intended when an access spanned multiple
      fields (for example a 32-bit access to the location of the MSI Message
      Data field with the high 16 bits not being covered by any known field).
      Remove it and derive which fields not to write to from the accessed
      fields' emulation masks: When they're all ones, there's no point in
      doing any host write.
      
      This fixes a secondary issue at once: We obviously shouldn't make any
      host write attempt when already the host read failed.
      
      This is XSA-128.
      Signed-off-by: NJan Beulich <jbeulich@suse.com>
      Reviewed-by: NStefano Stabellini <stefano.stabellini@eu.citrix.com>
      5c83b2f5
  4. 09 4月, 2013 2 次提交
  5. 01 3月, 2013 1 次提交
    • P
      hw: include hw header files with full paths · 83c9f4ca
      Paolo Bonzini 提交于
      Done with this script:
      
      cd hw
      for i in `find . -name '*.h' | sed 's/^..//'`; do
        echo '\,^#.*include.*["<]'$i'[">], s,'$i',hw/&,'
      done | sed -i -f - `find . -type f`
      
      This is so that paths remain valid as files are moved.
      
      Instead, files in hw/dataplane are referenced with the relative path.
      We know they are not going to move to include/, and they are the only
      include files that are in subdirectories _and_ move.
      Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      83c9f4ca
  6. 17 12月, 2012 1 次提交
  7. 15 10月, 2012 1 次提交
  8. 14 9月, 2012 1 次提交
  9. 22 6月, 2012 3 次提交