kernel: update to stable 6.18.49 and enable securityfs #65
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/stable-6.18.49-securityfs"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Import the signed kernel.org 6.18.49 tarball and enable CONFIG_SECURITYFS for runtime security-policy inspection. Preserve the 861-path local overlay, built-in ZFS 2.4.2, and every other generated config setting. The 6.18.44 baseline config reproduced the fleet SHA256 6d63400ab5835821759e960fc3f6aaa22fe98d11862981f08bbf1893f91f6d72. scripts/diffconfig shows only SECURITYFS n -> y. Both upstream tarball signatures were verified against Greg Kroah-Hartman fingerprint 647F28654894E3BD457199BE38DBBDC86092693E. No overlay conflicts; repository retains one root and existing trunk ancestry. All source work performed on the cluster case-sensitive filesystem. Release and canary-first fleet deployment through native Binjovi, with per-node progress and shell logs. No PostgreSQL huge-page allocation, IPVS removal, ZFS version change, or ptrace sysctl change.