)]}'
{
  "commit": "07ceaf98800519ef9c5dc893af00f1fe1f9144e4",
  "tree": "cd082239429f6870ebd9f78df3df0e1677fe97b4",
  "parents": [
    "84cbd63f87c1d246f51ec8eee5367a5588f367fd"
  ],
  "author": {
    "name": "Alex Williamson",
    "email": "alex.williamson@redhat.com",
    "time": "Tue Apr 28 11:14:02 2015 -0600"
  },
  "committer": {
    "name": "Alex Williamson",
    "email": "alex.williamson@redhat.com",
    "time": "Tue Apr 28 11:14:02 2015 -0600"
  },
  "message": "vfio-pci: Further fix BAR size overflow\n\nIn an analysis by Laszlo, the resulting type of our calculation for\nthe end of the MSI-X table, and thus the start of memory after the\ntable, is uint32_t.  We\u0027re therefore not correctly preventing the\ncorner case overflow that we intended to fix here where a BAR \u003e\u003d4G\ncould place the MSI-X table to end exactly at the 4G boundary.  The\nMSI-X table offset is defined by the hardware spec to 32bits, so we\nsimply use a cast rather than changing data structure types.  This\nscenario is purely theoretically, typically the MSI-X table is located\nat the front of the BAR.\n\nReported-by: Laszlo Ersek \u003clersek@redhat.com\u003e\nReviewed-by: Laszlo Ersek \u003clersek@redhat.com\u003e\nSigned-off-by: Alex Williamson \u003calex.williamson@redhat.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "cd15b20990d7a9c01c51351dd102096096e4d1ae",
      "old_mode": 33188,
      "old_path": "hw/vfio/pci.c",
      "new_id": "495f5fda8e8bee169cc164c29a37aea58acc2645",
      "new_mode": 33188,
      "new_path": "hw/vfio/pci.c"
    }
  ]
}