)]}'
{
  "commit": "899649b7d4ead76c19e39251ca886eebe3f811a8",
  "tree": "a86eae8128cf6f271ada3b4c4e4eb43238f56233",
  "parents": [
    "9dbdfd23b7638d054f3b0e70c64dfb9f297f2a9f"
  ],
  "author": {
    "name": "Alex Williamson",
    "email": "alex.williamson@redhat.com",
    "time": "Wed Oct 10 09:10:32 2012 -0600"
  },
  "committer": {
    "name": "Alex Williamson",
    "email": "alex.williamson@redhat.com",
    "time": "Wed Oct 10 09:10:32 2012 -0600"
  },
  "message": "vfio: Fix PCI INTx disable consistency\n\nThe virq_disabled flag tracks the userspace view of INTx masking\nacross interrupt mode changes, but we\u0027re not consistently applying\nthis to the interrupt and masking handler notion of the device.\nCurrently if the user sets DisINTx while in MSI or MSIX mode, then\nreturns to INTx mode (ex. rebooting a qemu guest), the hardware has\nDisINTx+, but the management of INTx thinks it\u0027s enabled, making it\nimpossible to actually clear DisINTx.  Fix this by updating the\nhandler state when INTx is re-enabled.\n\nCc: stable@vger.kernel.org\nSigned-off-by: Alex Williamson \u003calex.williamson@redhat.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "c8139a598f846973c535026d91883edc94eabcc3",
      "old_mode": 33188,
      "old_path": "drivers/vfio/pci/vfio_pci_intrs.c",
      "new_id": "3639371fa697e63e9bf6d3e5ccc49453e5ecff76",
      "new_mode": 33188,
      "new_path": "drivers/vfio/pci/vfio_pci_intrs.c"
    }
  ]
}