)]}'
{
  "log": [
    {
      "commit": "788257d6101d986ac8f2741aaa35974af47f574c",
      "tree": "332d877e09d8b5de6a4bdfba8111dd04e84a722b",
      "parents": [
        "9a311b96c3065f362e3348cb5d7af1a57ca6bff9"
      ],
      "author": {
        "name": "Arnd Bergmann",
        "email": "arnd@arndb.de",
        "time": "Mon Jan 24 10:14:12 2011 +0100"
      },
      "committer": {
        "name": "Arnd Bergmann",
        "email": "arnd@arndb.de",
        "time": "Wed Mar 02 22:27:48 2011 +0100"
      },
      "message": "ufs: remove the BKL\n\nThis introduces a new per-superblock mutex in UFS to replace\nthe big kernel lock. I have been careful to avoid nested\ncalls to lock_ufs and to get the lock order right with\nrespect to other mutexes, in particular lock_super.\n\nI did not make any attempt to prove that the big kernel\nlock is not needed in a particular place in the code,\nwhich is very possible.\n\nThe mutex has a significant performance impact, so it is only\nused on SMP or PREEMPT configurations.\n\nAs Nick Piggin noticed, any allocation inside of the lock\nmay end up deadlocking when we get to ufs_getfrag_block\nin the reclaim task, so we now use GFP_NOFS.\n\nSigned-off-by: Arnd Bergmann \u003carnd@arndb.de\u003e\nTested-by: Nick Bowler \u003cnbowler@elliptictech.com\u003e\nCc: Evgeniy Dushistov \u003cdushistov@mail.ru\u003e\nCc: Nick Piggin \u003cnpiggin@gmail.com\u003e\n"
    },
    {
      "commit": "6de5bd128d381ad88ac6d419a5e597048eb468cf",
      "tree": "7b3a0440f645c6e98367a87b1ca0ed1e0df204dd",
      "parents": [
        "7ff52efdca367d4bfe2449bd3d4a1f8172c5953a"
      ],
      "author": {
        "name": "Arnd Bergmann",
        "email": "arnd@arndb.de",
        "time": "Sat Sep 11 18:00:57 2010 +0200"
      },
      "committer": {
        "name": "Arnd Bergmann",
        "email": "arnd@arndb.de",
        "time": "Thu Oct 21 15:44:13 2010 +0200"
      },
      "message": "BKL: introduce CONFIG_BKL.\n\nWith all the patches we have queued in the BKL removal tree, only a\nfew dozen modules are left that actually rely on the BKL, and even\nthere are lots of low-hanging fruit. We need to decide what to do\nabout them, this patch illustrates one of the options:\n\nEvery user of the BKL is marked as \u0027depends on BKL\u0027 in Kconfig,\nand the CONFIG_BKL becomes a user-visible option. If it gets\ndisabled, no BKL using module can be built any more and the BKL\ncode itself is compiled out.\n\nThe one exception is file locking, which is practically always\nenabled and does a \u0027select BKL\u0027 instead. This effectively forces\nCONFIG_BKL to be enabled until we have solved the fs/lockd\nmess and can apply the patch that removes the BKL from fs/locks.c.\n\nSigned-off-by: Arnd Bergmann \u003carnd@arndb.de\u003e\n"
    },
    {
      "commit": "a276a52f9f1b1059bddade71df18ceb6481534a6",
      "tree": "ed72cb42a8e01f2b25207a077ecad378e77a1ae2",
      "parents": [
        "8af915ba1d1eae1f9f31fa8c5db8040492dc4785"
      ],
      "author": {
        "name": "Alexey Dobriyan",
        "email": "adobriyan@gmail.com",
        "time": "Thu Jan 22 11:05:02 2009 +0300"
      },
      "committer": {
        "name": "Alexey Dobriyan",
        "email": "adobriyan@gmail.com",
        "time": "Thu Jan 22 13:16:00 2009 +0300"
      },
      "message": "fs/Kconfig: move ufs out\n\nSigned-off-by: Alexey Dobriyan \u003cadobriyan@gmail.com\u003e\n"
    }
  ]
}