)]}'
{
  "commit": "ae6bd7f9b46a29af52ebfac25d395757e2031d0d",
  "tree": "f3359e6efbab5b57269bcbf38e7091cd80623e0d",
  "parents": [
    "b20fe56cd285dbbf64874ec9d1c81f8a8ac2f821"
  ],
  "author": {
    "name": "Filipe Manana",
    "email": "fdmanana@suse.com",
    "time": "Thu Feb 29 10:37:04 2024 +0000"
  },
  "committer": {
    "name": "David Sterba",
    "email": "dsterba@suse.com",
    "time": "Tue Mar 05 18:11:07 2024 +0100"
  },
  "message": "btrfs: fix off-by-one chunk length calculation at contains_pending_extent()\n\nAt contains_pending_extent() the value of the end offset of a chunk we\nfound in the device\u0027s allocation state io tree is inclusive, so when\nwe calculate the length we pass to the in_range() macro, we must sum\n1 to the expression \"physical_end - physical_offset\".\n\nIn practice the wrong calculation should be harmless as chunks sizes\nare never 1 byte and we should never have 1 byte ranges of unallocated\nspace. Nevertheless fix the wrong calculation.\n\nReported-by: Alex Lyakas \u003calex.lyakas@zadara.com\u003e\nLink: https://lore.kernel.org/linux-btrfs/CAOcd+r30e-f4R-5x-S7sV22RJPe7+pgwherA6xqN2_qe7o4XTg@mail.gmail.com/\nFixes: 1c11b63eff2a (\"btrfs: replace pending/pinned chunks lists with io tree\")\nCC: stable@vger.kernel.org # 6.1+\nReviewed-by: Josef Bacik \u003cjosef@toxicpanda.com\u003e\nReviewed-by: Qu Wenruo \u003cwqu@suse.com\u003e\nSigned-off-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nSigned-off-by: David Sterba \u003cdsterba@suse.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "5239b76775ba47ab9f43e113085fae16f019323e",
      "old_mode": 33188,
      "old_path": "fs/btrfs/volumes.c",
      "new_id": "e49935a54da0a398a672ac4c79d2e007a532a913",
      "new_mode": 33188,
      "new_path": "fs/btrfs/volumes.c"
    }
  ]
}