)]}'
{
  "commit": "951427ba709f7082124e31bb6d41b79d9219bcd4",
  "tree": "420ccf65ad0eac1cc92c5ea44250bf785446dc6c",
  "parents": [
    "cc92ce5f58879399309fea3f548e387252ee9bee"
  ],
  "author": {
    "name": "Megan Dahl",
    "email": "megan@schedmd.com",
    "time": "Fri Aug 29 15:18:46 2025 -0600"
  },
  "committer": {
    "name": "Danny Auble",
    "email": "da@schedmd.com",
    "time": "Wed Sep 03 13:31:20 2025 -0600"
  },
  "message": "slurmctld - Prevent reserved gres from being used by the wrong jobs\n\nBefore it was possible for the gres in a reservation to be used by a job\nnot requesting the reservation. This was because reservations reserve a\nspecific gres bit, but sock_gres-\u003ebits_any_sock\u0027s bitmap still included all\nthe gres bits, even those allocated to reservations. Additionally, before\nit was possible for a job requesting the reservation to be allocated a gres\nbit that was not reserved due to the same reason.\n\nThis modifies _handle_gres_exc_bit_and_not(), now renamed to\n_handle_gres_exc_bit_restrict(), so that now in the case of\nresv_exc_ptr-\u003egres_js_inc the bits_by_sock bitmap is restricted to only\ngres bits in the reservation. This function is now also called on\nsock_gres-\u003ebits_any_sock in the case no core topology is defined, which\ncan be the case for gres with a type defined.\n\nTicket: 21862\nChangelog: slurmctld - Fix how gres with cores or a type defined are\n selected to prevent jobs not using reservations from being allocated\n reserved gres and vice versa.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "9502a8e1a4829d2bdaadf10acca92c366434caf6",
      "old_mode": 33188,
      "old_path": "src/plugins/select/cons_tres/gres_sock_list.c",
      "new_id": "ebdc42ff4f3701d1ae2c2a79213a9043b69927f9",
      "new_mode": 33188,
      "new_path": "src/plugins/select/cons_tres/gres_sock_list.c"
    }
  ]
}