Repository navigation
Check security modules and mount topology in the native view entry - #6823
Clear1nsight wants to merge 1 commit into
Conversation
|
Delivery verified at exact head Hosted run 42322752936, attempt 1, completed success at that head: plan passed; replay skipped. This is repository planning/onboarding validation, not native or scientific replay. All 57 committed file Git identities, sizes and modes match the independently reviewed export. The changed-file set contains only the new archive, in one commit on canonical base The two new mocked-constructor suites each compiled and ran once; all four steps returned zero with known waits, both EOFs and exact runtime bytes. Both full compiler streams retain five disclosed indentation warnings. Expected outer exit 137 is whole-owned-group retirement and is separate from the test oracle. The conservative new debit is 64 seconds; recorded aggregate 1,520.890533479/2,400 seconds, with complete physical/preparation/review/publication/final costs OPEN_NOT_ZERO. Canonical handoff · hub pointer. The full caller proof and integration remain incomplete at the applied Ubuntu binutils effect transfer and the parent/compiler-property/query/fallback joins. No production entry, actual kernel query, original science, measured optimization or original activity credit is claimed. No source/research window is reopened by this delivery. |
Change and mathematical scope
Add a concrete native-entry proposal with actual bounded LSM enumeration, mount census and held-FD mount joins, plus conditional kernel proofs and two new mocked-constructor control suites. The complete caller proof and connected parent integration remain open; this is a completed scoped native prerequisite, not a full-caller qualification or performance claim.
The proposed 53,074-byte C source has SHA256
e1740fc6c901e09477ff0d934a920ca51dfe1a4b199d14e3433e155f1ef30fb2. It checks the complete capability/Landlock result, uses 129 slots for a 128-mount bound, validates exact returned masks and string bounds, joins real held-object unique mount IDs, and checks the source-owned two-clone view relation. Source bounds are 31 lifetime FD births, peak 13 tracked / 15 actual FDs, and 268 successful-path acquisition calls within a 288-attempt cap.For the explicit prospective Linux v6.12 model with miscellaneous handlers, core dumping and module loading disabled, this successor omits the predecessor's private binfmt-instance and forced CORE setup. It preserves inherited CORE limits and ordinary self resource operations. Original native trust conditions, including initial Landlock/seccomp/BPF state, remain unissued qualification premises. No host configuration or selected full-caller source was changed.
Task and overlap
Original investigation: PR #6321. Entry predecessor: PR #6819, exact head
65b0c1b71e849cbbe2160c211811d18d43e25e55; connected source/refusal predecessor: PR #6818, head1479ccf2ec0bc29b7bf741a2d613d79e1f9ec19e. Retain the original full caller from PR #6744.Canonical base:
7c49fe32c55de02c2c873655c804b16e4c3fef0a. Publication head:f497188c5125ce6e2bba67c9d2831bbc62945ea5. Scope is refined to this accepted native implementation; the original whole-caller objective is unchanged. The existing FD/error owner and prior native source are reused, rather than replaced by a supplied descriptor or compatibility flag. All-state/all-author searches and exact source/head inspection covered the implicated native and compiler work; bounded search is not global novelty. Exact compiler sources/data in #6362/#6366 and conditional frontiers in #6434/#6454 retain their separate scopes and credit.Validation
One independently admitted serial attempt compiled and ran each NEW mocked control once. All four steps returned zero, with known waits, both EOFs and no recorded errors. The policy control had empty stdout/stderr; the native-fact control matched its exact 64-byte success line and empty stderr. Each compile retained five indentation warnings, included in full and independently read. This is not a warning-free build.
The controls exercise actual proposed constructors through mocked native boundaries and independent positive, malformed, capacity, raw-error and policy oracles. No production entry, actual namespace/LSM/mount probe, original science or unchanged predecessor controls ran. Expected outer exit 137 is deliberate whole-owned-group retirement; acceptance rests on the four step records and raw captures.
The isolated archive contains 57 exact files. Passive integrity check passed:
No executable native/scientific replay hook is registered. The recorded absolute-path guard is actual local evidence, not a portable replay command. The new conservative policy debit is 64 seconds; recorded aggregate 1,520.890533479 / 2,400 seconds. Complete physical, preparation, Pro/review, reporting, publication, final metadata and historical costs remain
OPEN_NOT_ZERO. Hosted outcomes will be recorded against the submitted head.Credit
Retain Chris R / Clear1nsight, Douglas R. Colkitt, repository and predecessor contributors, including unpaidmoon / Cursor-Grok's primary-preserving cleanup. Substantial ChatGPT Pro, OpenAI Codex and GPT-6.1-sol Max source implementation and independent agent review assistance is disclosed. AI/finite control acceptance is distinct from human, proof-kernel and native qualification. New material is Apache-2.0; external kernel source retains its own licensing and exact acquisition identities.
Open next questions
The remaining mathematical transfer is the exact applied Ubuntu binutils 2.42-4ubuntu2.10 assembler/linker/BFD effect frontier. The ordered 54-patch series and source archives are retained, but patch bodies, applied runtime units and configuration have not yet supplied that proof. A release announcement or executable-byte match does not replace it.
After that source transfer, implement and independently accept the complete parent compiler-property/specs/fallback acquisition and checked query transport in the existing owners. The frozen caller still lacks those joins. Current image/resource/funding/native/scientific admission follows separately. No complete caller or original activity credit is claimed here. See the archive README and exact remaining-source report for the smallest resolving input.