)]}'
{
  "commit": "4fadd7bb20a1e7c774ed88dc703d8fbcd00ff917",
  "tree": "a6f3df6f19d27e81f35a93f8858b73bd4273f420",
  "parents": [
    "1ba50bbe93ebb98e83b174a85eff76af430c4e5b"
  ],
  "author": {
    "name": "Christoph Hellwig",
    "email": "hch@lst.de",
    "time": "Mon Aug 03 23:28:06 2009 +0200"
  },
  "committer": {
    "name": "Al Viro",
    "email": "viro@zeniv.linux.org.uk",
    "time": "Thu Sep 24 07:47:39 2009 -0400"
  },
  "message": "freeze_bdev: kill bd_mount_sem\n\nNow that we have the freeze count there is not much reason for bd_mount_sem\nanymore.  The actual freeze/thaw operations are serialized using the\nbd_fsfreeze_mutex, and the only other place we take bd_mount_sem is\nget_sb_bdev which tries to prevent mounting a filesystem while the block\ndevice is frozen.  Instead of add a check for bd_fsfreeze_count and\nreturn -EBUSY if a filesystem is frozen.  While that is a change in user\nvisible behaviour a failing mount is much better for this case rather\nthan having the mount process stuck uninterruptible for a long time.\n\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "5d1ed50bd46c591c1ef63b312c4844d013f5239b",
      "old_mode": 33188,
      "old_path": "fs/block_dev.c",
      "new_id": "22506eb4a58e1523ba45dc497e6bde195e0b32f5",
      "new_mode": 33188,
      "new_path": "fs/block_dev.c"
    },
    {
      "type": "modify",
      "old_id": "4906e2d8f40083647c5d4696431d0fcf54daca39",
      "old_mode": 33188,
      "old_path": "fs/super.c",
      "new_id": "1cb26a3e3df0e69cca14bf94b2dc88a34a4bbf68",
      "new_mode": 33188,
      "new_path": "fs/super.c"
    },
    {
      "type": "modify",
      "old_id": "cbb7724c11d39a2539d7cf4fa4ae3fa2ab27f2ef",
      "old_mode": 33188,
      "old_path": "include/linux/fs.h",
      "new_id": "72dfbd4239746baa7a8707698c76543442c11155",
      "new_mode": 33188,
      "new_path": "include/linux/fs.h"
    }
  ]
}