)]}'
{
  "commit": "7d410d5efe04e42a6cd959bfe6d59d559fdf8b25",
  "tree": "e93d993c9353b5b1e5adbe74711d58ff72899836",
  "parents": [
    "5fba5a571858ce2d787fdaf55814e42725bfa895"
  ],
  "author": {
    "name": "Filipe Manana",
    "email": "fdmanana@suse.com",
    "time": "Tue Nov 21 13:38:33 2023 +0000"
  },
  "committer": {
    "name": "David Sterba",
    "email": "dsterba@suse.com",
    "time": "Thu Nov 23 22:27:46 2023 +0100"
  },
  "message": "btrfs: make error messages more clear when getting a chunk map\n\nWhen getting a chunk map, at btrfs_get_chunk_map(), we do some sanity\nchecks to verify we found a chunk map and that map found covers the\nlogical address the caller passed in. However the messages aren\u0027t very\nclear in the sense that don\u0027t mention the issue is with a chunk map and\none of them prints the \u0027length\u0027 argument as if it were the end offset of\nthe requested range (while the in the string format we use %llu-%llu\nwhich suggests a range, and the second %llu-%llu is actually a range for\nthe chunk map). So improve these two details in the error messages.\n\nCC: stable@vger.kernel.org # 5.4+\nReviewed-by: Josef Bacik \u003cjosef@toxicpanda.com\u003e\nSigned-off-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nReviewed-by: David Sterba \u003cdsterba@suse.com\u003e\nSigned-off-by: David Sterba \u003cdsterba@suse.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "1775ae0998b0a67483012d11d8c3f0d4aac27be8",
      "old_mode": 33188,
      "old_path": "fs/btrfs/volumes.c",
      "new_id": "3b61c47306c015f5b9e6ee27bede8834855d005b",
      "new_mode": 33188,
      "new_path": "fs/btrfs/volumes.c"
    }
  ]
}