)]}'
{
  "commit": "6c1e65798c1d9547eb8e413684398942db37ce71",
  "tree": "594b22eb5f5763d6f44fd1f1fc98411646235de6",
  "parents": [
    "c94e7ce36d57106a5138e5f595bebbf1a81b3ffb"
  ],
  "author": {
    "name": "Will Deacon",
    "email": "will@kernel.org",
    "time": "Wed Dec 01 11:02:20 2021 +0000"
  },
  "committer": {
    "name": "Will Deacon",
    "email": "will@kernel.org",
    "time": "Wed Dec 01 15:48:20 2021 +0000"
  },
  "message": "virtio_ring: Fix querying of maximum DMA mapping size for virtio device\n\nvirtio_max_dma_size() returns the maximum DMA mapping size of the virtio\ndevice by querying dma_max_mapping_size() for the device when the DMA\nAPI is in use for the vring. Unfortunately, the device passed is\ninitialised by register_virtio_device() and does not inherit the DMA\nconfiguration from its parent, resulting in SWIOTLB errors when bouncing\nis enabled and the default 256K mapping limit (IO_TLB_SEGSIZE) is not\nrespected:\n\n  | virtio-pci 0000:00:01.0: swiotlb buffer is full (sz: 294912 bytes), total 1024 (slots), used 725 (slots)\n\nFollow the pattern used elsewhere in the virtio_ring code when calling\ninto the DMA layer and pass the parent device to dma_max_mapping_size()\ninstead.\n\nCc: Marc Zyngier \u003cmaz@kernel.org\u003e\nCc: Quentin Perret \u003cqperret@google.com\u003e\nCc: \"Michael S. Tsirkin\" \u003cmst@redhat.com\u003e\nCc: Jason Wang \u003cjasowang@redhat.com\u003e\nSigned-off-by: Will Deacon \u003cwill@kernel.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "00f64f2f8b72b45fcdb230223aa689adff620bcd",
      "old_mode": 33188,
      "old_path": "drivers/virtio/virtio_ring.c",
      "new_id": "c294d04b0eb90c9aade97e47bd89280555aad819",
      "new_mode": 33188,
      "new_path": "drivers/virtio/virtio_ring.c"
    }
  ]
}