)]}'
{
  "commit": "05fa199d45c54a9bda7aa3ae6537253d6f097aa9",
  "tree": "cfdcdd04bfcef7d0dcb47fad93ba8fa676349dd3",
  "parents": [
    "05f54c13cd0c33694eec39a265475c5d6cf223cf"
  ],
  "author": {
    "name": "Hugh Dickins",
    "email": "hugh@veritas.com",
    "time": "Thu Apr 16 21:58:12 2009 +0100"
  },
  "committer": {
    "name": "Linus Torvalds",
    "email": "torvalds@linux-foundation.org",
    "time": "Thu Apr 16 14:41:25 2009 -0700"
  },
  "message": "mm: pass correct mm when growing stack\n\nTetsuo Handa reports seeing the WARN_ON(current-\u003emm \u003d\u003d NULL) in\nsecurity_vm_enough_memory(), when do_execve() is touching the\ntarget mm\u0027s stack, to set up its args and environment.\n\nYes, a UMH_NO_WAIT or UMH_WAIT_PROC call_usermodehelper() spawns\nan mm-less kernel thread to do the exec.  And in any case, that\nvm_enough_memory check when growing stack ought to be done on the\ntarget mm, not on the execer\u0027s mm (though apart from the warning,\nit only makes a slight tweak to OVERCOMMIT_NEVER behaviour).\n\nReported-by: Tetsuo Handa \u003cpenguin-kernel@i-love.sakura.ne.jp\u003e\nSigned-off-by: Hugh Dickins \u003chugh@veritas.com\u003e\nCc: stable@kernel.org\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "4a3841186c11100f05e01f498c13794621b1edff",
      "old_mode": 33188,
      "old_path": "mm/mmap.c",
      "new_id": "3303d1ba8e87aca1ba34ca74f92d0cd9038de396",
      "new_mode": 33188,
      "new_path": "mm/mmap.c"
    }
  ]
}