)]}'
{
  "commit": "70fa99f445a6fabe4b46f188cc665cd469cd8293",
  "tree": "7a258a28ea076d84ad7092edef18f9756d9c2002",
  "parents": [
    "8cb98a725e7397c9de25ebd77c00b1d5f2d8351e"
  ],
  "author": {
    "name": "Eric Blake",
    "email": "eblake@redhat.com",
    "time": "Thu Jun 08 08:56:36 2023 -0500"
  },
  "committer": {
    "name": "Eric Blake",
    "email": "eblake@redhat.com",
    "time": "Wed Jul 19 15:26:13 2023 -0500"
  },
  "message": "nbd/client: Add safety check on chunk payload length\n\nOur existing use of structured replies either reads into a qiov capped\nat 32M (NBD_CMD_READ) or caps allocation to 1000 bytes (see\nNBD_MAX_MALLOC_PAYLOAD in block/nbd.c).  But the existing length\nchecks are rather late; if we encounter a buggy (or malicious) server\nthat sends a super-large payload length, we should drop the connection\nright then rather than assuming the layer on top will be careful.\nThis becomes more important when we permit 64-bit lengths which are\neven more likely to have the potential for attempted denial of service\nabuse.\n\nSigned-off-by: Eric Blake \u003ceblake@redhat.com\u003e\nReviewed-by: Vladimir Sementsov-Ogievskiy \u003cvsementsov@yandex-team.ru\u003e\nMessage-ID: \u003c20230608135653.2918540-8-eblake@redhat.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "ea3590ca3d07091155e8596b79cd9be3bbd8c2e0",
      "old_mode": 33188,
      "old_path": "nbd/client.c",
      "new_id": "1b5569556fe7480983a7e10be739878a87e35692",
      "new_mode": 33188,
      "new_path": "nbd/client.c"
    }
  ]
}