)]}'
{
  "commit": "58e40801bfed5a8befc0881594820fa0a0baa4a1",
  "tree": "95e4a14b20a20ff168c6c249289a7b420002955d",
  "parents": [
    "7b92fcfd6de7801450ae3b9e44f5ca78accba555"
  ],
  "author": {
    "name": "Zhiwei Zhang",
    "email": "zhangzhiwei@bitintelligence.io",
    "time": "Tue Jul 21 14:03:12 2026 +0800"
  },
  "committer": {
    "name": "Leon Romanovsky",
    "email": "leonro@nvidia.com",
    "time": "Sun Sep 06 03:02:53 2026 -0400"
  },
  "message": "pyverbs: Update MW rkey after type 2 bind\n\nset_bind_wr() assigns the incremented rkey to the bind WR but leaves MW.rkey\nunchanged. After the bind succeeds, applications that publish MW.rkey to the\npeer send the old rkey, while the NIC has already bound the MW with the new\nrkey. Remote access using the stale rkey consequently fails with a remote\naccess error.\n\nSynchronize MW.rkey with the rkey of successfully posted IBV_WR_BIND_MW\nrequests. When posting a WR list partially fails, only Bind WRs before bad_wr\nare updated, since those are the requests accepted by ibv_post_send().\n\nSigned-off-by: Zhiwei Zhang \u003czhangzhiwei@bitintelligence.io\u003e\nSigned-off-by: Leon Romanovsky \u003cleonro@nvidia.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "a14fd93eb36da060338d35be9f23af397aa7bdd2",
      "old_mode": 33188,
      "old_path": "pyverbs/qp.pyx",
      "new_id": "abf86357d76376a505d0867e89ffb62ad7b23582",
      "new_mode": 33188,
      "new_path": "pyverbs/qp.pyx"
    },
    {
      "type": "modify",
      "old_id": "ef75f4b242866f5c6dd33239d0ce548b49845170",
      "old_mode": 33188,
      "old_path": "tests/test_mr.py",
      "new_id": "b7ef04e8c32be703abb4166f159ff1ea4f35e15d",
      "new_mode": 33188,
      "new_path": "tests/test_mr.py"
    }
  ]
}