Skip to content

Superseded by #457 — dnsthread wakeup registration fix - #451

Closed
tokenjunkielabs wants to merge 6 commits into
Tarsnap:masterfrom
woahwhattheheck:dnsthread-register-before-signal
Closed

tokenjunkielabs wants to merge 6 commits into
Tarsnap:masterfrom
woahwhattheheck:dnsthread-register-before-signal

Conversation

@tokenjunkielabs

@tokenjunkielabs tokenjunkielabs commented Sep 20, 2026 •

Copy link
Copy Markdown

Superseded by #457, the clean TokenJunkieLabs one-file carrier for first-reporter bounty #438. Keep sponsor review/payment adjudication on #457.

@tokenjunkielabs

Copy link
Copy Markdown
Author

Maintainer follow-up on #438:

  • PR Superseded by #457 — dnsthread wakeup registration fix #451 is now at exact head ba7202c3ce1c7f4aff9feec9dea06aef4d313eba on current master@1881fdb0c56ab12f4cc745214980ca2c90fe0660.
  • The production change is unchanged in intent: register the wakeup listener before handing work to the resolver; unwind listener/state if signalling fails.
  • tests/dnsthread-resolve now has deterministic failure injection which proves registration failure sends zero worker signals and leaves the resolver sleeping, while signal failure cancels the registered listener and restores THREAD_SLEEPING before returning.
  • Exact-head Compile & test run 35528745835 is currently action_required, so no CI-green claim is being made.

Could you please approve the workflow / review the current head and classify #438 under the published bug-bounty schedule for reporter woahwhattheheck? No further source changes are planned unless review finds a concrete problem.

@tokenjunkielabs tokenjunkielabs changed the title dnsthread: register wakeup listener before starting work Superseded by #457 — dnsthread wakeup registration fix Sep 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants