)]}'
{
  "commit": "334714e4bdf8868c17a7650a7502ba1c90a8721f",
  "tree": "c123d60ba12324874098c7890a1471809c15e0c1",
  "parents": [
    "17f7f7ef5dc2f4607ba8cdf486cb25cc564cd6f7"
  ],
  "author": {
    "name": "Fan Wu",
    "email": "wufan@kernel.org",
    "time": "Mon Sep 21 15:05:16 2026 -0700"
  },
  "committer": {
    "name": "Mikulas Patocka",
    "email": "mpatocka@redhat.com",
    "time": "Tue Oct 13 17:31:14 2026 +0200"
  },
  "message": "dm-verity: clear LSM integrity state on suspend\n\ndm-verity publishes its root hash and signature state to LSMs in\nverity_preresume(). LSMs such as IPE store this information in the block\ndevice\u0027s security blob and use it to authorize access to files.\n\nThe original LSM integration relied on DM_TARGET_IMMUTABLE to prevent\nverity from being replaced by a different target type. However, DM allows\ntables containing a DM_TARGET_WILDCARD target to replace immutable\ntargets. The block device can then retain the old integrity state even\nthough its data is no longer verified by dm-verity.\n\nClear the published root hash and signature state in verity_postsuspend()\nso that the block device does not retain stale dm-verity attributes after\nthe verity target is replaced.\n\nAssisted-by: gpt-6-astra\nSigned-off-by: Fan Wu \u003cwufan@kernel.org\u003e\nSigned-off-by: Mikulas Patocka \u003cmpatocka@redhat.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "cb105ccc47ecb1171bb795b0ef481bf911535e26",
      "old_mode": 33188,
      "old_path": "drivers/md/dm-verity-target.c",
      "new_id": "6d589867623c01706aff36d9f49a9998e0919a70",
      "new_mode": 33188,
      "new_path": "drivers/md/dm-verity-target.c"
    }
  ]
}