)]}'
{
  "commit": "d67fd44f697dff293d7cdc29af929241b669affe",
  "tree": "0c1e26c0d0669db52f4a50f6cb15a9e7fa4b2ea6",
  "parents": [
    "5ff132c07aa155d759ab3da946c86351313d3020"
  ],
  "author": {
    "name": "Nikolay Borisov",
    "email": "kernel@kyup.com",
    "time": "Wed Aug 17 16:18:46 2016 -0400"
  },
  "committer": {
    "name": "Jeff Layton",
    "email": "jlayton@redhat.com",
    "time": "Thu Aug 18 13:49:41 2016 -0400"
  },
  "message": "locks: Filter /proc/locks output on proc pid ns\n\nOn busy container servers reading /proc/locks shows all the locks\ncreated by all clients. This can cause large latency spikes. In my\ncase I observed lsof taking up to 5-10 seconds while processing around\n50k locks. Fix this by limiting the locks shown only to those created\nin the same pidns as the one the proc fs was mounted in. When reading\n/proc/locks from the init_pid_ns proc instance then perform no\nfiltering\n\n[ jlayton: reformat comments for 80 columns ]\n\nSigned-off-by: Nikolay Borisov \u003ckernel@kyup.com\u003e\nSuggested-by: Eric W. Biederman \u003cebiederm@xmission.com\u003e\nSigned-off-by: Jeff Layton \u003cjlayton@redhat.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "ee1b15f6fc135c33e2e0564eb5e10db927080533",
      "old_mode": 33188,
      "old_path": "fs/locks.c",
      "new_id": "7e428b78be074506b4cf6ca03b15c16497b2abbb",
      "new_mode": 33188,
      "new_path": "fs/locks.c"
    }
  ]
}