)]}'
{
  "commit": "cc1676d917f32504dbadc858fa790bc524c9f0da",
  "tree": "d665d5ad0a844a6b1aff74deb4c8aa01c7596135",
  "parents": [
    "365b94ae67d2915d412b593d47449a6bffed9d37"
  ],
  "author": {
    "name": "Jan Kara",
    "email": "jack@suse.cz",
    "time": "Thu May 03 14:47:56 2012 +0200"
  },
  "committer": {
    "name": "Fengguang Wu",
    "email": "fengguang.wu@intel.com",
    "time": "Sun May 06 13:43:38 2012 +0800"
  },
  "message": "writeback: Move requeueing when I_SYNC set to writeback_sb_inodes()\n\nWhen writeback_single_inode() is called on inode which has I_SYNC already\nset while doing WB_SYNC_NONE, inode is moved to b_more_io list. However\nthis makes sense only if the caller is flusher thread. For other callers of\nwriteback_single_inode() it doesn\u0027t really make sense and may be even wrong\n- flusher thread may be doing WB_SYNC_ALL writeback in parallel.\n\nSo we move requeueing from writeback_single_inode() to writeback_sb_inodes().\n\nReviewed-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Jan Kara \u003cjack@suse.cz\u003e\nSigned-off-by: Fengguang Wu \u003cfengguang.wu@intel.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "dd41437b7a1fe49507f79e43efba1c33590a43c7",
      "old_mode": 33188,
      "old_path": "fs/fs-writeback.c",
      "new_id": "65cd1476922624c49b403cb3859f8d02fb3f1d22",
      "new_mode": 33188,
      "new_path": "fs/fs-writeback.c"
    },
    {
      "type": "modify",
      "old_id": "7b81887b023f9deb9f46994722c03542ad97a6db",
      "old_mode": 33188,
      "old_path": "include/trace/events/writeback.h",
      "new_id": "b453d92c225347f95605db68e33dd50b628fb0f0",
      "new_mode": 33188,
      "new_path": "include/trace/events/writeback.h"
    }
  ]
}