)]}'
{
  "commit": "a6dbd429d8dd3382bbd9594b8d2ec74843a260d9",
  "tree": "9cc6426da748996e4e1cc61d446052838703434f",
  "parents": [
    "33b258086441dd07e00133c79fcd8cbc6a76d737"
  ],
  "author": {
    "name": "Josef Bacik",
    "email": "josef@redhat.com",
    "time": "Wed Nov 11 15:53:34 2009 -0500"
  },
  "committer": {
    "name": "Chris Mason",
    "email": "chris.mason@oracle.com",
    "time": "Wed Nov 11 15:53:34 2009 -0500"
  },
  "message": "Btrfs: fix panic when trying to destroy a newly allocated\n\nThere is a problem where iget5_locked will look for an inode, not find it, and\nthen subsequently try to allocate it.  Another CPU will have raced in and\nallocated the inode instead, so when iget5_locked gets the inode spin lock again\nand does a search, it finds the new inode.  So it goes ahead and calls\ndestroy_inode on the inode it just allocated.  The problem is we don\u0027t set\nBTRFS_I(inode)-\u003eroot until the new inode is completely initialized.  This patch\nmakes us set root to NULL when alloc\u0027ing a new inode, so when we get to\nbtrfs_destroy_inode and we see that root is NULL we can just free up the memory\nand continue on.  This fixes the panic\n\nhttp://www.kerneloops.org/submitresult.php?number\u003d812690\n\nThanks,\n\nSigned-off-by: Josef Bacik \u003cjosef@redhat.com\u003e\nSigned-off-by: Chris Mason \u003cchris.mason@oracle.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "d3d7d46a6af2d06f7f251bd7192e79d93896ad1b",
      "old_mode": 33188,
      "old_path": "fs/btrfs/inode.c",
      "new_id": "ee92801fc5db789d1b2a5673dafab89d69c2cca4",
      "new_mode": 33188,
      "new_path": "fs/btrfs/inode.c"
    }
  ]
}