)]}'
{
  "commit": "e669e800fc9ef8806af5c5578249ab758a4f8a5a",
  "tree": "4c2c07c155752b784429633df46797f76deb6760",
  "parents": [
    "719c6819ed9a9838520fa732f9861918dc693bda"
  ],
  "author": {
    "name": "Stefan Hajnoczi",
    "email": "stefanha@redhat.com",
    "time": "Mon May 06 15:06:22 2024 -0400"
  },
  "committer": {
    "name": "Kevin Wolf",
    "email": "kwolf@redhat.com",
    "time": "Mon Jun 10 11:05:43 2024 +0200"
  },
  "message": "aio: warn about iohandler_ctx special casing\n\nThe main loop has two AioContexts: qemu_aio_context and iohandler_ctx.\nThe main loop runs them both, but nested aio_poll() calls on\nqemu_aio_context exclude iohandler_ctx.\n\nWhich one should qemu_get_current_aio_context() return when called from\nthe main loop? Document that it\u0027s always qemu_aio_context.\n\nThis has subtle effects on functions that use\nqemu_get_current_aio_context(). For example, aio_co_reschedule_self()\ndoes not work when moving from iohandler_ctx to qemu_aio_context because\nqemu_get_current_aio_context() does not differentiate these two\nAioContexts.\n\nDocument this in order to reduce the chance of future bugs.\n\nSigned-off-by: Stefan Hajnoczi \u003cstefanha@redhat.com\u003e\nMessage-ID: \u003c20240506190622.56095-3-stefanha@redhat.com\u003e\nReviewed-by: Kevin Wolf \u003ckwolf@redhat.com\u003e\nSigned-off-by: Kevin Wolf \u003ckwolf@redhat.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "8378553eb9dde7dac7a149de4ca1751ad2a068bb",
      "old_mode": 33188,
      "old_path": "include/block/aio.h",
      "new_id": "4ee81936ed5e67e361d51168c25cefa5f1af0bb7",
      "new_mode": 33188,
      "new_path": "include/block/aio.h"
    }
  ]
}