)]}'
{
  "commit": "86f162f4c75ceb6daf43165469eeeca1bc3d4639",
  "tree": "bca0e9d28d636fbaefb1846bdb85d9b57708df11",
  "parents": [
    "1c1e618ddd15f69fd87ccea596769f78c8065504"
  ],
  "author": {
    "name": "Jiri Slaby",
    "email": "jslaby@suse.cz",
    "time": "Sat Nov 14 17:37:04 2009 +0100"
  },
  "committer": {
    "name": "Jiri Slaby",
    "email": "jirislaby@gmail.com",
    "time": "Fri Jul 16 09:48:47 2010 +0200"
  },
  "message": "rlimits: do security check under task_lock\n\nDo security_task_setrlimit under task_lock. Other tasks may change\nlimits under our hands while we are checking limits inside the\nfunction. From now on, they can\u0027t.\n\nNote that all the security work is done under a spinlock here now.\nSecurity hooks count with that, they are called from interrupt context\n(like security_task_kill) and with spinlocks already held (e.g.\ncapable-\u003esecurity_capable).\n\nSigned-off-by: Jiri Slaby \u003cjslaby@suse.cz\u003e\nAcked-by: James Morris \u003cjmorris@namei.org\u003e\nCc: Heiko Carstens \u003cheiko.carstens@de.ibm.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "9dbcbbcce15385e54a20f0949d7cd5c0461dee7d",
      "old_mode": 33188,
      "old_path": "kernel/sys.c",
      "new_id": "c762eebdebf7bdae98506279ae535fac6dfead4d",
      "new_mode": 33188,
      "new_path": "kernel/sys.c"
    }
  ]
}