DragonFlyBSD Kernel Audit
DF-2616 / fix_v1_too_strict.txt
← back to finding ↓ download raw
# fix v1 (alignment-strict) false-positive evidence — captured from the v1 fixed-kernel boot
# (root fs hammer2; every line is a LEGITIMATE on-disk bref the v1 check rejected,
#  proving hammer2 legitimately stores radix-N blocks at 1KB-aligned offsets)

hammer2_chain_load_data: illegal data_off geometry 000000001526e40b.03
hammer2_chain_load_data: illegal data_off geometry 000000001526040d.03
hammer2_chain_load_data: illegal data_off geometry 000000001526d40b.03
hammer2_chain_load_data: illegal data_off geometry 000000001525140b.03
hammer2_chain_load_data: illegal data_off geometry 0000000015251c0b.03
hammer2_chain_load_data: illegal data_off geometry 000000001526b40b.03
hammer2_chain_load_data: illegal data_off geometry 000000001523cc0b.03
hammer2_chain_load_data: illegal data_off geometry 000000001525840b.03
hammer2_chain_load_data: illegal data_off geometry 000000001526a40c.03
hammer2_chain_load_data: illegal data_off geometry 000000001a56500d.03

# radix nibble of the trailing hex: 0b/0c/0d = radix 11/12/13; e.g. 0x1526e40b:
# lbase 0x1526e400 (1KB-aligned), radix 11 (2KB block) — legal per freemap
# granularity; v2 accepts it, v1 rejected it and degraded the boot.