Repository navigation
v0.0.2
·
232 commits
to main
since this release
- ELF files with extended section numbering (0xff00 or more sections:
e_shnum0,e_shstrndxSHN_XINDEX, symbol section indexes in.symtab_shndx) are read; before, kflow saw no sections in them. Synthetic test. - A kernel module's relocations are applied in place instead of in a second copy of the file (output unchanged on nf_tables.ko and ext4.ko).
- A raw arm64 kernel
Image(also gzip-compressed, as Ubuntu's arm64vmlinuz) or an x86bzImage/vmlinuznow gets a message naming the tool that turns it into an ELF (vmlinux-to-elf, or extract-vmlinux on x86), not just "is not an ELF file"; in IDA, the warning for a database with none of the three tables says the same for a rawImage/vmlinuzloaded as a binary file. - Checked on two more kernels, Ubuntu 24.04's 6.8.0-149-generic for x86_64 and for arm64 (each
vmlinuzthrough vmlinux-to-elf): x86_64 11,027 BUG/WARN sites (8,259 WARN), 8,304 static-key sites (all keys named), 632 exception-table entries (the 45 WRMSR and 41 RDMSR entries all sit onwrmsr/rdmsr); arm64 10,803 BUG/WARN sites (8,085 WARN, allbrk #0x800), 31,250 static-key sites (all keys named, 22,918 of them tracepoints), 935 exception-table entries. README table rows added. - README "Try it": the quickest sample is the
vmlinuzyour own Linux machine boots, through vmlinux-to-elf (with the copy step for a root-only/boot). - Static-key comments say when the site jumps: "jumps to X when the key is off" (
static_branch_likelysites) or "... is on" (static_branch_unlikely), from the kernel's rule that a site is a jump when the key's state XOR the entry's branch bit is set (jump_label_type()). Found by a judge-style review. - Modules: a static key inside an imported array was named after the NEXT import (Debian 13
bridge.ko:sprintf+0x40fornf_hooks_needed + 0x270): each import now gets a 64 KB slot and a key in it is named from that import, exactly (checked againstreadelf -r). Found by a judge-style review. - README opens with who it is for and a before/after of three real sites (objdump instruction vs kflow's comment). Found by a judge-style review.
- New action kflow: List static-key sites: every static-key site with its key, likely/unlikely, whether its bytes are a jump to the target now, the target and the function (the chooser's filter finds all sites of one key). Suggested by a judge-style review. Fake-IDA test on the demo, GKI 5.10, nf_tables.ko and a stripped vmlinux (no jump table: one warning).
- Keys inside an array of keys are named after the array: when nothing is named within 64 bytes before a key, the nearest name up to 4 KB before it is used (
cpu_hwcap_keys+0x50: 24,470 sites on Android GKI 5.10 that showed only an address; alsonf_hooks_needed,sched_feat_keys,cgroup_bpf_enabled_key). Every key on the seven test kernels now has a name (demo kernel: 9,237 of 9,237, was 8,898). In IDA the name comes from IDA's name list (get_nlist_idxand its neighbour); the fake-IDA test checks that IDA and the command line give every key the same name. Found by a judge-style review. - Annotate also adds a user data reference from each static-key site to its key, so the key's cross references (X) list every site it patches; Remove deletes only the ones kflow added (recorded in the database, also after a rebase), and a reference you made yourself stays. Suggested by a judge-style review; fake-IDA tests only.
- Names in comments and in the static-key list never come from IDA's placeholder names (
unk_...,byte_..., which IDA gives referenced addresses, keys included once Annotate adds its key references): kflow asks for the name withget_ea_name(ea, GN_NOT_DUMMY). Found by a pre-release review of the IDA calls; the fake-IDA test'sget_namenow returns placeholder names like IDA, and the test fails if one shows.
Built by an AI agent (Claude, operated by Nightshift Labs). Not yet run in real IDA.