Bug report

Bug description:

Bug report

Bug description:

This is a filtered list of issues found in the _hashlib, _hmac, and HACL*-facade C extension modules by @devdanzin's LLM-assisted review tool (see Disclosure section at the end) and triaged by me.

_hashopenssl.c

• 32: bug (GIL issue) [33,45]
• 34: bug (OpenSSL misuse)
• 38: invalid C API usage
• 40: need investigation
• 43: under consideration (cosmetic)
• 47: need investigation (read out of lock) [35,36]
• 49: under consideration (cosmetic)
• 🔴 52: invalid hash types previously raised SystemError, but not abort (this is deliberate, if we have invalid hash types somehow, it may be more than a reason to report the bug and get it fixed upstream rather than silently catching the exception)

_hmacmodule.c

• 31/42: Ensure that HMAC objects are properly initialized #155843
• 33/45: bug (GIL issue) [32]
• 37: build issue [known]
• 🔴 50: not an issue (py_hmac_hinfo was claimed to be lacking a visitor method but none of its members are containers)

MD5, SHA-*, BLAKE2-*

• 35/36: Ensure that HACL* states are not read concurrently #155835 [47]
• 39: bug (error code ignored)
• 41: bug (init) but addressed in gh-155833: GC-untrack MD5/SHA* objects before freeing the HACL* state #155834 directly (SHA3 missing initialization)
• 44: Ensure that cryptographic objects are GC-untracked first #155833
• 🔴 46: not planned (same rationale as 52, but for BLAKE-2 update())
• 48: Ensure that BLAKE-2 objects are fully initialized before being GC-tracked #155830
• 🔴 51: Fallible PyType_GetModuleState usage. More generally, getting the state of a module is inconsistently achieved in extension modules and we should decide whether (1) to consistently abort on DEBUG builds (2) abort on non-DEBUG builds via a fatal error (to prevent possibly expensive checks). Currently, code works because we assume non-subclassability in general, but we may consider a more defensive approach.

Disclosure

This review was carried out with AI assistance (Claude Code), using cpython-review-toolkit for the C modules and code-review-toolkit for the Python layer. Every reproduced entry was run on a real interpreter with a control arm before being recorded, and every file:line was read in the source rather than inferred. That does not make the set error-free — the companion gist lists the corrections this list has already needed — so entries should be judged on their evidence, not on the length of the list.

CPython versions tested on:

CPython main branch

Operating systems tested on:

No response