)]}'
{
  "commit": "f7008d0aeba21396b3422df135b692ae701bd0c8",
  "tree": "6c51cbd3f7377f0394551988ce3b646fe2b31133",
  "parents": [
    "024910cbac323ab2e5ad6d7fa7958799b04b9728"
  ],
  "author": {
    "name": "Christoph Hellwig",
    "email": "hch@infradead.org",
    "time": "Mon Feb 15 22:02:19 2010 +0000"
  },
  "committer": {
    "name": "Alex Elder",
    "email": "aelder@sgi.com",
    "time": "Mon Mar 01 16:35:17 2010 -0600"
  },
  "message": "xfs: fix xfs_fsblock_t tracing\n\nUsing a static buffer in xfs_fmtfsblock means we can corrupt traces if\nmultiple CPUs hit this code path at the same.  Just remove xfs_fmtfsblock\nfor now and print the block number purely numerical.  If we want the\nNULLFSBLOCK and NULLSTARTBLOCK formatting back the best way would be\na decoding plugin in the trace-cmd userspace command.\n\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nReviewed-by: Dave Chinner \u003cdavid@fromorbit.com\u003e\nSigned-off-by: Alex Elder \u003caelder@sgi.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "856eb3c8d6054b5937cad5d4c327e737095a3da2",
      "old_mode": 33188,
      "old_path": "fs/xfs/linux-2.6/xfs_trace.c",
      "new_id": "5a107601e9696889df87bd28a4147f3c90cbbf8f",
      "new_mode": 33188,
      "new_path": "fs/xfs/linux-2.6/xfs_trace.c"
    },
    {
      "type": "modify",
      "old_id": "87f9fad80aacbe44445eba664a93a89c36fe6b12",
      "old_mode": 33188,
      "old_path": "fs/xfs/linux-2.6/xfs_trace.h",
      "new_id": "fcaa62f0799e7e80135da20bb877d4ed98bc1892",
      "new_mode": 33188,
      "new_path": "fs/xfs/linux-2.6/xfs_trace.h"
    }
  ]
}
