[gburd]

__memp_dirty refetches the page with __memp_fget when it upgrades a snapshot page to a writable copy. For a snapshot-safe txn that fetch can return DB_SNAPSHOT_CONFLICT (SSI mechanism (b), __memp_si_rwconflict). Only DB_LOCK_DEADLOCK skipped the BDB3010 "error getting a page for writing" message, so every such SSI abort also printed it, though the caller just aborts the txn.

Found during v2026.10.7.2 qualification. The SSI write-skew fixes (#257/#258) raise the abort rate on contended workloads. ssi_livelock on FreeBSD 14.5 x86_64 printed BDB3010 30–89 times in 3 s. A counting probe showed every txn that printed it returned DB_SNAPSHOT_CONFLICT or DB_SNAPSHOT_UNSAFE and aborted, and no txn returned another code. On Linux the same run prints none.

Fix: skip the message for the two SSI codes, as for a deadlock. The return value is unchanged. One line; no format or ABI change.

Backport: for the next LTS patch (v2026.10.7.3), not v2026.10.7.2. It is a cosmetic log-noise fix, and v2026.10.7.2 is already qualified.

[github-actions]

ABI diff vs v2026.10.8 (libabigail — authoritative)

abidiff exit bitmask: 0

Removed exported symbols (nm -D, _NNNN version suffix normalized)

None.

---

Advisory: libabigail/nm is the authoritative binary-ABI check; Coccinelle is complementary source-level early warning. See dist/cocci/README.md.

[github-actions]

Coccinelle convention checks

No new violations. ✅

Resolved since baseline (3) -- update dist/cocci/baseline.txt to lock these in.

rule_mutex_unbalanced|MUTEX_UNBALANCED|src/btree/bt_curadj.c|return (ret);
rule_mutex_unbalanced|MUTEX_UNBALANCED|src/crypto/mersenne/mt19937db.c|return (ret);
rule_mutex_unbalanced|MUTEX_UNBALANCED|src/mp/mp_register.c|return (ret);