)]}'
{
  "commit": "bcbb7bf6ccde7cb969a5642879832bc84ebf06a3",
  "tree": "18a39891555fe3acd6b4197fd097f10745777b4b",
  "parents": [
    "b1c62645758eb438179e3a0769168cb7b0a94d6b"
  ],
  "author": {
    "name": "Jens Axboe",
    "email": "axboe@kernel.dk",
    "time": "Thu Mar 10 12:59:35 2022 -0700"
  },
  "committer": {
    "name": "Jens Axboe",
    "email": "axboe@kernel.dk",
    "time": "Thu Mar 10 13:05:25 2022 -0700"
  },
  "message": "io_uring: allow submissions to continue on error\n\nBy default, io_uring will stop submitting a batch of requests if we run\ninto an error submitting a request. This isn\u0027t strictly necessary, as\nthe error result is passed out-of-band via a CQE anyway. And it can be\na bit confusing for some applications.\n\nProvide a way to setup a ring that will continue submitting on error,\nwhen the error CQE has been posted.\n\nThere\u0027s still one case that will break out of submission. If we fail\nallocating a request, then we\u0027ll still return -ENOMEM. We could in theory\npost a CQE for that condition too even if we never got a request. Leave\nthat for a potential followup.\n\nReported-by: Dylan Yudaken \u003cdylany@fb.com\u003e\nSigned-off-by: Jens Axboe \u003caxboe@kernel.dk\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "3145c9cacee09dec0c15602ada859f2f8c4110ad",
      "old_mode": 33188,
      "old_path": "fs/io_uring.c",
      "new_id": "229b31d644ef7f799a0325a2a417eb7f2fb46fdf",
      "new_mode": 33188,
      "new_path": "fs/io_uring.c"
    },
    {
      "type": "modify",
      "old_id": "8bd4bfdd9a8988cecc0dc620122e9f2789b228b7",
      "old_mode": 33188,
      "old_path": "include/uapi/linux/io_uring.h",
      "new_id": "d2be4eb220082b8042b325aa45ac94c17c64bfb9",
      "new_mode": 33188,
      "new_path": "include/uapi/linux/io_uring.h"
    }
  ]
}