)]}'
{
  "commit": "70e2f1d4fa02274a7ee85e09f7befa783391681b",
  "tree": "5d852421041b3ccc512d80a96825fe07b5978317",
  "parents": [
    "d843d75e9e3037056c5a39d9f9affe798763aa8d"
  ],
  "author": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Tue Feb 01 16:29:28 2022 +0300"
  },
  "committer": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Tue Feb 01 16:29:28 2022 +0300"
  },
  "message": "Cache: fixed race in ngx_http_file_cache_forced_expire().\n\nDuring configuration reload two cache managers might exist for a short\ntime.  If both tried to delete the same cache node, the \"ignore long locked\ninactive cache entry\" alert appeared in logs.  Additionally,\nngx_http_file_cache_forced_expire() might be also called by worker\nprocesses, with similar results.\n\nFix is to ignore cache nodes being deleted, similarly to how it is\ndone in ngx_http_file_cache_expire() since 3755:76e3a93821b1.  This\nwas somehow missed in 7002:ab199f0eb8e8, when ignoring long locked\ncache entries was introduced in ngx_http_file_cache_forced_expire().\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "c40093bca61cbd199c0c06e85640614f85241c8b",
      "old_mode": 33188,
      "old_path": "src/http/ngx_http_file_cache.c",
      "new_id": "4d2f6c42c70e69d686e361794b6223e562b01286",
      "new_mode": 33188,
      "new_path": "src/http/ngx_http_file_cache.c"
    }
  ]
}