Repository navigation
Conversation
yunwei37
left a comment
There was a problem hiding this comment.
Reviewed the head 356052e4 as a content change: research page
ebpf-link-controller-reconciliation.md + same-length .zh.md twin (326 lines
each), an index.md entry (4 lines), and seo-data bookkeeping.
Paired, indexed, and the seo-data edits are diff-shaped rather than rewrites.
Checks are green.
AI-generated response; a maintainer will review and follow up later
yunwei37
left a comment
There was a problem hiding this comment.
Reviewed at the current head, the merge of master that resolved the conflict reported on this pull request.
The generated index files were resolved as a union with no duplicate headings.
Verification and the resolution per file are in the pull request conversation
comment; state is mergeable_state=blocked, which is the approval gate. A
maintainer's approval and merge are what remain.
AI-generated response; a maintainer will review and follow up later
2a3412f to
5b9487c
Compare
yunwei37
left a comment
There was a problem hiding this comment.
Reviewed head 5b9487ca33: the previous review point (175c09a813) moved onto today's main. The branch's own content is unchanged.
Evidence: for every path this pull request changes (5 files), the git blob at this head equals the blob at 175c09a8. The apparent line churn against main comes from files main moved on, not from this branch.
So the earlier review of the change itself still stands, and this head is no longer behind its base. Merge readiness is unchanged: it waits on a maintainer's decision.
AI patrol review
|
Verdict: ready to merge Head Merge is the maintainer's to make: eunomia.dev is not in the small-repository group, so the patrol does not merge it. AI patrol review |
yunwei37
left a comment
There was a problem hiding this comment.
Verdict: ready to merge
The review above stands: this head's content is blob-identical to the previously reviewed revision, so only the rebase onto today's main moved. Checks green, mergeable, level with the base.
AI patrol review
5b9487c to
5eb4154
Compare
yunwei37
left a comment
There was a problem hiding this comment.
Verdict: ready to merge once CI is green
Reviewed head 5eb41544. Every changed file is blob-identical to the previously reviewed revision (5b9487ca), including the reconciliation-report index edits (ef1dc059, e511fbce) and the daily-record contract fix (5eb41544 itself, byte-identical to what was reviewed when it was the head's last commit): docs/research/ebpf-link-controller-reconciliation{,.zh}.md, both index edits, .github/seo-data/daily/2026-09-21.md. Merge base unchanged at f8a2cce8.
Content is unchanged: the report separates ownership of a persistent eBPF link (the loader that created it) from the reconcile loop that may adopt it, and requires the loop to converge on the loader's intent rather than overwrite it, which is the property the code paths it cites actually enforce.
Checks on this head: GitGuardian Security Checks success, validate and deploy-static-app queued. The verdict turns to merge-ready when those report green.
AI patrol review
5eb4154 to
27758cb
Compare
yunwei37
left a comment
There was a problem hiding this comment.
Verdict: ready to merge once CI is green
Reviewed at head 27758cb5, which is the previously reviewed 5eb41544 moved onto today's base. Nothing in the change itself moved: for the range merge-base(main, head)..head, git patch-id --stable is identical before and after, and the changed file list with its line counts is unchanged. The earlier review (5912544569) therefore stands as written, and so does its verdict.
The rebase re-queued this head's checks, so the previous head's green results do not carry over; read the new run, not the old one. Merge stays with a maintainer.
AI patrol review
|
Verdict: ready to merge This is the verdict for head Merge is the maintainer's to make: eunomia.dev is not in the small-repository group, so the patrol does not merge it. AI patrol review |
Summary
bpf_linkownership after controller crash or restartEvidence and scope
2026-09-07..09-13; GSC has finalized observed rows through2026-09-12but still lacks a complete comparable seven-day or 28-day windowEditorial boundary
Before this publication the newest ten published reports are 7 eBPF-centered / 1 pure Agent / 2 adjacent systems. The oldest item rotating out is eBPF-centered, so this eBPF-centered report preserves the window at 7 / 1 / 2.
Open PR #207 (post-reboot pinned state reconstruction) and PR #208 (evolving BPF interface negotiation) remain unmerged reserved boundaries and are not counted as published content. Today's question begins after userspace controller state is lost while the kernel link is still live, which is distinct from planned transactional upgrade and from post-reboot object reconstruction.
Validation
Final acceptance requires terminal-green final-head CI, complete diff/generated-output self-review, explicit review-thread inspection, squash merge, exact-merge production deployment, bilingual production verification, sitemap verification, and exactly one compact top-level merged-PR closeout comment. The recurring operations schedule remains enabled regardless of blockers.