)]}'
{
  "commit": "0c88ee5b7523e76e290d558c28cd0be48ffad597",
  "tree": "c603735c1012c231a4cc2d315bb30f795e1c4781",
  "parents": [
    "50aa98bad056a17655864a4d71ebc32d95c629a7"
  ],
  "author": {
    "name": "Heiko Carstens",
    "email": "heiko.carstens@de.ibm.com",
    "time": "Fri Sep 11 10:28:58 2009 +0200"
  },
  "committer": {
    "name": "Martin Schwidefsky",
    "email": "schwidefsky@de.ibm.com",
    "time": "Fri Sep 11 10:29:53 2009 +0200"
  },
  "message": "[S390] Initialize __LC_THREAD_INFO early.\n\n\"lockdep: Fix backtraces\" reveales a bug in early setup code: when\nlockdep tries to save a stack backtrace before setup_arch has been\ncalled the lowcore pointer for the current thread info pointer isn\u0027t\ninitialized yet.\nHowever our save stack backtrace code relies on it. If the pointer\nisn\u0027t initialized the saved backtrace will have zero entries.\nlockdep however relies (correctly) on the fact that that cannot\nhappen.\nA write access to some random memory region is the result.\n\nFix this by initializing the thread info pointer early.\n\nSigned-off-by: Heiko Carstens \u003cheiko.carstens@de.ibm.com\u003e\nSigned-off-by: Martin Schwidefsky \u003cschwidefsky@de.ibm.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "2ced846065b7a61e340fc88d9b390a4416ead542",
      "old_mode": 33188,
      "old_path": "arch/s390/kernel/head31.S",
      "new_id": "602b508cd4c41d3ef4792d6fbcdaae300c5aff39",
      "new_mode": 33188,
      "new_path": "arch/s390/kernel/head31.S"
    },
    {
      "type": "modify",
      "old_id": "65667b2e65cee6fdd3ed71f104ee326d4ec13d86",
      "old_mode": 33188,
      "old_path": "arch/s390/kernel/head64.S",
      "new_id": "bdcb3f05bcd1949fd2f592b1c93c53eb18e10b08",
      "new_mode": 33188,
      "new_path": "arch/s390/kernel/head64.S"
    }
  ]
}