)]}'
{
  "commit": "5fd8ee4fe82b38abe40a397a791a06f43e922aee",
  "tree": "d5aab311d1206b9a1420b7c015d056ec32c14e95",
  "parents": [
    "03c43ede280f944d5f79cdb70a467950f97f79d2"
  ],
  "author": {
    "name": "LongPing Wei",
    "email": "weilongping@oppo.com",
    "time": "Tue Mar 25 10:12:26 2025 +0800"
  },
  "committer": {
    "name": "LongPing Wei",
    "email": "weilongping@oppo.com",
    "time": "Tue Mar 25 10:29:34 2025 +0800"
  },
  "message": "avb: synchronize optional parameter list to latest\n\nhttps://gitlab.com/cryptsetup/cryptsetup/wikis/DMVerity#optional-parameters\nOptional parameters\n\nignore_corruption: Log corrupted blocks, but allow read operations to proceed normally.\nAvailable since: 1.2.0 (no proper version set) (kernel 4.1)\n\nrestart_on_corruption: Restart the system when a corrupted block is discovered.\nThis option is not compatible with ignore_corruption and panic_on_corruption and requires user space support to avoid restart loops.\nAvailable since: 1.2.0 (no proper version set) (kernel 4.1)\n\npanic_on_corruption: Panic the system when a corrupted block is discovered.\nThis option is not compatible with ignore_corruption and restart_on_corruption and requires user space support to avoid restart loops.\nAvailable since: 1.7.0 (kernel 5.9)\n\nrestart_on_error: Restart the system when an I/O error is detected.\nThis option can be combined with the restart_on_corruption option.\nAvailable since: 1.10.0 (kernel 6.12)\n\npanic_on_error: Panic the device when an I/O error is detected.\nThis option is not compatible with the restart_on_error option but can be combined with the panic_on_corruption option.\nAvailable since: 1.10.0 (kernel 6.12)\n\nignore_zero_blocks: Do not verify blocks that are expected to contain zeroes and always return zeroes instead.\nThis may be useful if the partition contains unused blocks that are not guaranteed to contain zeroes.\nAvailable since: 1.3.0 (kernel 4.5)\n\ncheck_at_most_once: Verify data blocks only the first time they are read from the data device, rather than every time.\nIt provides a reduced level of security because only offline tampering of the data device\u0027s content will be detected, not online tampering.\nAvailable since: 1.4.0 (kernel 4.17)\n\nroot_hash_sig_key_desc \u003ckey_description\u003e: The PKCS7 signature to validate the root hash during the creation of the device.\nThe key must be in trusted kernel keyring.\nVerification of roothash depends on the config DM_VERITY_VERIFY_ROOTHASH_SIG being set.\nAvailable since: 1.5.0 (kernel 5.4)\n\ntry_verify_in_tasklet: If possible, verify data blocks in kernel tasklet instead of workqueue. This option can reduce IO latency.\nAvailable since: 1.9.0 (kernel 6.0)\n\nBug: 401036538\nChange-Id: Ia3d1a6152b296bc1bea2feb872b4cad8e4a551db\nSigned-off-by: LongPing Wei \u003cweilongping@oppo.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "e2626759b0dcb76017519678056d0f6daa5d8931",
      "old_mode": 33188,
      "old_path": "avb/VtsSecurityAvbTest.cpp",
      "new_id": "ee0c3230050c72db6e2a61628ceb9c947cad71e9",
      "new_mode": 33188,
      "new_path": "avb/VtsSecurityAvbTest.cpp"
    }
  ]
}