)]}'
{
  "commit": "9747dd6fa98f2983f4dd09cd6dad1fa3d2a4c5f2",
  "tree": "f8e191827f6ff913d083a89028b1b732ef56b231",
  "parents": [
    "a6ad57fb4b5e9d68553f4440377b99f75588fa88"
  ],
  "author": {
    "name": "Paul Mackerras",
    "email": "paulus@samba.org",
    "time": "Sat Apr 30 10:01:40 2005 -0700"
  },
  "committer": {
    "name": "Linus Torvalds",
    "email": "torvalds@ppc970.osdl.org",
    "time": "Sat Apr 30 10:01:40 2005 -0700"
  },
  "message": "[PATCH] ppc64: fix 32-bit signal frame back link\n\nWhen the kernel creates a signal frame on the user stack, it puts the\nold stack pointer value at the beginning so that the signal frame is\nlinked into the chain of stack frames like any other frame.\nUnfortunately, for 32-bit processes we are writing the old stack\npointer as a 64-bit value rather than a 32-bit value, and the process\nsees that as a null pointer, since it only looks at the first 32 bits,\nwhich are zero since ppc is bigendian and the stack pointer is below\n4GB.  This bug is in SLES9 and RHEL4 too, hence the ccs.\n\nThis patch fixes the bug by making the signal code write the old stack\npointer as a u32 instead of an unsigned long.\n\nSigned-off-by: Paul Mackerras \u003cpaulus@samba.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "b0e167db6af9c68f49949d409abc747d3119842f",
      "old_mode": 33188,
      "old_path": "arch/ppc64/kernel/signal32.c",
      "new_id": "3c2fa5c284c04ef223c468c2df53f6c7676dc20a",
      "new_mode": 33188,
      "new_path": "arch/ppc64/kernel/signal32.c"
    }
  ]
}
