)]}'
{
  "commit": "812805ff3b0c7069dc94d4a031960b4e2c80beac",
  "tree": "f01f46aa18ff4dbfc76483087ef85974efcbf8c2",
  "parents": [
    "b610eff230f2ce92fd48502d71ad0993792f73d3"
  ],
  "author": {
    "name": "Jens Axboe",
    "email": "axboe@kernel.dk",
    "time": "Mon May 16 23:05:51 2022 +0200"
  },
  "committer": {
    "name": "Akilesh Kailash",
    "email": "akailash@google.com",
    "time": "Wed Jun 01 16:15:27 2022 +0000"
  },
  "message": "UPSTREAM: io_uring: always use original task when preparing req identity\n\nIf the ring is setup with IORING_SETUP_IOPOLL and we have more than\none task doing submissions on a ring, we can up in a situation where\nwe assign the context from the current task rather than the request\noriginator.\n\nAlways use req-\u003etask rather than assume it\u0027s the same as current.\n\nNo upstream patch exists for this issue, as only older kernels with\nthe non-native workers have this problem.\n\nBug: 233078742\nReported-by: Kyle Zeng \u003czengyhkyle@gmail.com\u003e\nSigned-off-by: Jens Axboe \u003caxboe@kernel.dk\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\nSigned-off-by: Akilesh Kailash \u003cakailash@google.com\u003e\n(cherry picked from commit 29f077d070519a88a793fbc70f1e6484dc6d9e35\n from linux-5.10.y stable branch)\nChange-Id: I4cc543950a95e1df201fa9867c5e9c272fd54b6f\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "fd188b97215119183b7fac8268f0f644b3cf5095",
      "old_mode": 33188,
      "old_path": "fs/io_uring.c",
      "new_id": "d0c4928acec751ce6a994056c66b5cd04de7c825",
      "new_mode": 33188,
      "new_path": "fs/io_uring.c"
    }
  ]
}