)]}'
{
  "commit": "241f29fba6ab4c584eeb4e7f53302aa92d2c11f4",
  "tree": "fab24539e0523b0279ed3c056d432bfcc0e5a402",
  "parents": [
    "4b41a55fe53ce2da4823ffa3a5b94bd09bf2ab0d"
  ],
  "author": {
    "name": "Andrew Burgess",
    "email": "aburgess@redhat.com",
    "time": "Wed Oct 11 14:39:37 2023 +0100"
  },
  "committer": {
    "name": "Andrew Burgess",
    "email": "aburgess@redhat.com",
    "time": "Thu Oct 12 13:58:19 2023 +0100"
  },
  "message": "bfd/cache: change type used to track cached BFDs from int to unsigned\n\nWithin bfd/cache.c change the type for max_open_files and open_files\nvariables from int to unsigned.  As a consequence of this, the return\ntype for bfd_cache_max_open() is also changed from int to unsigned.\n\nWithin bfd_cache_max_open I\u0027ve left the local \u0027max\u0027 variable as an\nint, this should ensure that if the sysconf call fails, and returns\n-1, then the computed max value will be less than 10, which means\nmax_open_files will be set to 10.  If \u0027max\u0027 was changed to unsigned\nthen, should the sysconf call fail, we\u0027d end up with max becoming a\nvery large positive number ... which is clearly not what we want.\n\nAnd, while I was auditing how open_files is used, I added an assert\nwithin bfd_cache_delete to ensure that we don\u0027t try to reduce\nopen_files below zero.\n\nThere should be no user visible change with this commit.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "357a38da5998eee7a68109e013158c21ac34b773",
      "old_mode": 33188,
      "old_path": "bfd/cache.c",
      "new_id": "87c4bcd3148f36bddaa9a7689f1ae25140ba719f",
      "new_mode": 33188,
      "new_path": "bfd/cache.c"
    }
  ]
}