)]}'
{
  "commit": "b32a30ad91e075d30dcc63398fb23c7a8c3a2152",
  "tree": "941a89ec4cb5d6116a3a367239a9f6cfa9c3d0bc",
  "parents": [
    "a3a399d7802481e0a58d65f837a14753fdf346c7"
  ],
  "author": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Mon Jun 22 18:02:58 2020 +0300"
  },
  "committer": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Mon Jun 22 18:02:58 2020 +0300"
  },
  "message": "Large block sizes on Linux are now ignored (ticket #1168).\n\nNFS on Linux is known to report wsize as a block size (in both f_bsize\nand f_frsize, both in statfs() and statvfs()).  On the other hand,\ntypical file system block sizes on Linux (ext2/ext3/ext4, XFS) are limited\nto pagesize.  (With FAT, block sizes can be at least up to 512k in\nextreme cases, but this doesn\u0027t really matter, see below.)\nTo avoid too aggressive cache clearing on NFS volumes on Linux, block\nsizes larger than pagesize are now ignored.\n\nNote that it is safe to ignore large block sizes.  Since 3899:e7cd13b7f759\n(1.0.1) cache size is calculated based on fstat() st_blocks, and rounding\nto file system block size is preserved mostly for Windows.\n\nNote well that on other OSes valid block sizes seen are at least up\nto 65536.  In particular, UFS on FreeBSD is known to work well with block\nand fragment sizes set to 65536.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "482d327637e5af7485e05aace8755652ef1962f7",
      "old_mode": 33188,
      "old_path": "src/os/unix/ngx_files.c",
      "new_id": "7e8e58fe71cace3da7f8f6d63b07854b25b08f50",
      "new_mode": 33188,
      "new_path": "src/os/unix/ngx_files.c"
    }
  ]
}