)]}'
{
  "commit": "59ccded8ade31ed6f8906d6da9bb19414dcedbbd",
  "tree": "706887cdbc4acc80cee7e3f05770723b127c117d",
  "parents": [
    "84464ba0246b3366433d958cbdeac7ff57f741f5"
  ],
  "author": {
    "name": "Xie Bo",
    "email": "xb@ultrarisc.com",
    "time": "Mon Aug 03 09:32:26 2026 +0800"
  },
  "committer": {
    "name": "Will Deacon",
    "email": "will@kernel.org",
    "time": "Thu Aug 06 12:18:32 2026 +0000"
  },
  "message": "virtio: 9p: Order used ring updates before notifications\n\nvirtio_p9_do_io() signals the guest immediately after adding each\nrequest to the used ring. Unlike the block and net backends, it bypasses\nvirtio_queue__should_signal(), which provides the full memory barrier\nneeded between publishing used-\u003eidx and injecting the interrupt.\n\nOn weakly ordered architectures, the guest can therefore handle the\ninterrupt before the updated used-\u003eidx becomes visible. If it observes\nthe old index and goes back to sleep, the completed request can remain\nstuck indefinitely because no further interrupt is generated.\n\nThis was observed on RISC-V with two 9p RPCs blocked while the host\nused-\u003eidx was two entries ahead of the guest\u0027s last_used_idx.\n\nProcess all available requests first, then use\nvirtio_queue__should_signal() before notifying the guest. Besides\nproviding the required ordering, this also honors the driver\u0027s\nnotification suppression request.\n\nFixes: 1c7850f95903 (\"kvm tools: Add virtio-9p\")\nSigned-off-by: Xie Bo \u003cxb@ultrarisc.com\u003e\nSigned-off-by: Will Deacon \u003cwill@kernel.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "cf3e547d317339edf05aff6bfdfcb3f5e87b8df6",
      "old_mode": 33188,
      "old_path": "virtio/9p.c",
      "new_id": "fb08d0d90dcdea5560221e9bb966871fbac2d5bb",
      "new_mode": 33188,
      "new_path": "virtio/9p.c"
    }
  ]
}
