)]}'
{
  "commit": "2fb9d2689a0041b88b25bc3187eada2968e25995",
  "tree": "28c25b5092a209cd55d5d3f29dea827bdde70abe",
  "parents": [
    "5ab46b345e418747b3a52f0892680c0745c4223c"
  ],
  "author": {
    "name": "Oleg Nesterov",
    "email": "oleg@redhat.com",
    "time": "Thu Sep 03 19:21:45 2009 +0200"
  },
  "committer": {
    "name": "Jiri Slaby",
    "email": "jirislaby@gmail.com",
    "time": "Fri Jul 16 09:48:46 2010 +0200"
  },
  "message": "rlimits: make sure -\u003erlim_max never grows in sys_setrlimit\n\nMostly preparation for Jiri\u0027s changes, but probably makes sense anyway.\n\nsys_setrlimit() checks new_rlim.rlim_max \u003c\u003d old_rlim-\u003erlim_max, but when\nit takes task_lock() old_rlim-\u003erlim_max can be already lowered. Move this\ncheck under task_lock().\n\nCurrently this is not important, we can only race with our sub-thread,\nthis means the application is stupid. But when we change the code to allow\nthe update of !current task\u0027s limits, it becomes important to make sure\n-\u003erlim_max can be lowered \"reliably\" even if we race with the application\ndoing sys_setrlimit().\n\nSigned-off-by: Oleg Nesterov \u003coleg@redhat.com\u003e\nSigned-off-by: Jiri Slaby \u003cjslaby@suse.cz\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "f5183b08adfcd2f9c35ca2bd5a1cfd20d4966426",
      "old_mode": 33188,
      "old_path": "kernel/sys.c",
      "new_id": "f2b2d7aa3818aea0fe2f5cee208a99b1b046a449",
      "new_mode": 33188,
      "new_path": "kernel/sys.c"
    }
  ]
}