)]}'
{
  "commit": "2ac3de0bbf40ecf32875e0a28b592a5d97d0503e",
  "tree": "e58dc634c8fd81cc96b2358a2b56df80dd60dd62",
  "parents": [
    "8710ef1fa0715a331f967565a4eb56c6d4b4c15b"
  ],
  "author": {
    "name": "Benjamin Marzinski",
    "email": "bmarzins@redhat.com",
    "time": "Wed Apr 29 16:21:08 2026 -0400"
  },
  "committer": {
    "name": "Mikulas Patocka",
    "email": "mpatocka@redhat.com",
    "time": "Mon May 04 14:53:52 2026 +0200"
  },
  "message": "dm-ima: use active table\u0027s size if available\n\nIt is possible that the dm_ima_measure_on_* functions run at the same\ntime as a table is getting swapped, but before the md-\u003eima.active_table\nis updated by dm_ima_measure_on_device_resume(). Instead of using the\ncurrent device size, use the size of the active table that is being\nmeasured (assuming there is one), so the information is consistent.\nAlso, don\u0027t allocate a separate string to hold the capactiy. Just\nprint it directly to the measurement buffer.\n\nSigned-off-by: Benjamin Marzinski \u003cbmarzins@redhat.com\u003e\nSigned-off-by: Mikulas Patocka \u003cmpatocka@redhat.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "5e2efcd1de33aab241c7e795f8c8c332f04bca0b",
      "old_mode": 33188,
      "old_path": "drivers/md/dm-ima.c",
      "new_id": "5e7232582feb7a02758d83163d5a03593f90d2d1",
      "new_mode": 33188,
      "new_path": "drivers/md/dm-ima.c"
    },
    {
      "type": "modify",
      "old_id": "b240e0e4b6a1961916437635bc3ca6b87270f3b0",
      "old_mode": 33188,
      "old_path": "drivers/md/dm-ima.h",
      "new_id": "0ec013d1545cc12e959d1af53a59f9cae3eed2f1",
      "new_mode": 33188,
      "new_path": "drivers/md/dm-ima.h"
    }
  ]
}