[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699670CJEK1464D5PCED8MV":3,"skill-same:01M699670CJEK1464D5PCED8MV":73},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M699670CJEK1464D5PCED8MV","syzlang-vm-testing",null,"Verify syzkaller syscall descriptions (sys\u002Flinux\u002F*.txt) and seed programs (sys\u002Flinux\u002Ftest\u002F*) inside a QEMU VM using syz-manager -mode run-tests, syzbot buildroot images, and kernel dynamic_debug\u002Ftracing.","google\u002Fsyzkaller","google","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1342004?v=4","01M698VYEFDM0VJBZDYYJ2T83S","Google","01M6995Z4DBY2H54K638R4JANB",6412,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fsyzkaller\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fsyzlang-vm-testing\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"testing","syzlang vm testing","vm","kernel","linux","test","debug","run","tracing","verify","images","seed","tests","mode","manager","2026-11-10 10:12:30",false,"---\nname: syzlang-vm-testing\ndescription: >-\n  Verify syzkaller syscall descriptions (sys\u002Flinux\u002F*.txt) and seed programs (sys\u002Flinux\u002Ftest\u002F*)\n  inside a QEMU VM using syz-manager -mode run-tests, syzbot buildroot images, and kernel\n  dynamic_debug\u002Ftracing.\n---\n\n# Syzlang & Seed Program QEMU VM Verification\n\nUse this skill to verify new or updated Linux syscall descriptions (`sys\u002Flinux\u002F*.txt`), executor\nsetup (`executor\u002Fcommon_linux.h`), and seed programs (`sys\u002Flinux\u002Ftest\u002F*`) inside a QEMU VM.\n\nFor general syzlang description and seed authoring rules (and host-side parsing tests), see\n[`sys\u002FGEMINI.md`](..\u002F..\u002F..\u002Fsys\u002FGEMINI.md).\n\n## 1. Obtaining the VM Disk Image and Kernel\n\n1. **Userspace Disk Image (Buildroot)**:\n   If no disk image is available locally, download and decompress the standard syzkaller buildroot\n   image from `https:\u002F\u002Fstorage.googleapis.com\u002Fsyzkaller\u002Fimages\u002Fbuildroot-amd64-2025.05.gz`.\n\n2. **Kernel Image (`bzImage` and `vmlinux`)**:\n   - If the user provided a Linux kernel build directory or `bzImage` path, use it.\n   - Otherwise, visit `https:\u002F\u002Fsyzkaller.appspot.com\u002Fupstream\u002Fmanager\u002Fci-qemu-upstream`, download\n     the latest `kernel image` (`bzImage`) and `vmlinux` (if needed for coverage symbolization),\n     and decompress them.\n\n## 2. Running Seed Programs via `syz-manager -mode run-tests`\n\nBuild `syz-manager` and `syz-executor`:\n```bash\nCI=true .\u002Ftools\u002Fsyz-env make manager executor\n```\n\nCreate a minimal `syz-manager` config (e.g., `\u002Ftmp\u002Fruntest.cfg`):\n```json\n{\n\t\"name\": \"runtest\",\n\t\"target\": \"linux\u002Famd64\",\n\t\"http\": \"127.0.0.1:0\",\n\t\"workdir\": \"\u002Ftmp\u002Fsyz-runtest-workdir\",\n\t\"image\": \"\u002Ftmp\u002Fbuildroot-amd64.img\",\n\t\"syzkaller\": \".\",\n\t\"sandbox\": \"none\",\n\t\"procs\": 1,\n\t\"type\": \"qemu\",\n\t\"vm\": {\n\t\t\"count\": 1,\n\t\t\"kernel\": \"\u002Ftmp\u002FbzImage\",\n\t\t\"cmdline\": \"root=\u002Fdev\u002Fsda1\",\n\t\t\"cpu\": 2,\n\t\t\"mem\": 2048\n\t}\n}\n```\n- **KVM vs TCG**: By default on `linux\u002Famd64`, syzkaller passes\n  `-enable-kvm -cpu host,migratable=off` to QEMU. If KVM (`\u002Fdev\u002Fkvm`) is available on the host,\n  always use it. If KVM is not available, configure TCG in `vm.qemu_args` (e.g.,\n  `\"qemu_args\": \"-machine q35 -accel tcg -cpu max\"`) and be very patient, as booting an\n  instrumented kernel under software emulation takes several minutes.\n- **Sandbox**: If the seed program targets syscalls fuzzed under `\"sandbox\": \"namespace\"` in\n  production, also test with `\"sandbox\": \"namespace\"` to verify that devices or sockets created in\n  `init_net` work from child network namespaces.\n\nRun the specific seed test(s) with `-mode run-tests` and `-tests \u003Cprefix>`:\n```bash\n.\u002Fbin\u002Fsyz-manager -config \u002Ftmp\u002Fruntest.cfg -mode run-tests -tests \u003Cseed_name>\n```\n`syz-manager -mode run-tests` boots the QEMU VM, runs the machine check, and executes matching\n`sys\u002Flinux\u002Ftest\u002F\u003Cseed_name>` programs via both `syz-executor` (verifying KCOV coverage and that\nevery call returns the expected errno, `0` by default) and `pkg\u002Fcsource` C binaries. Pass `-debug`\nto dump full VM console and executor output.\n\n## 3. Debugging What the Program Actually Does in the Kernel\n\nA seed test passing with `errno=0` on every syscall is necessary, but for subsystems with\nasynchronous workqueues, tasklets, softirqs, or shared `mmap` rings (e.g., RDMA `rxe`, `io_uring`,\n`vhost`), the kicking syscall can return `0` even when the asynchronous worker immediately aborts\non a bad struct layout, ring offset, or key.\n\nWhen you need to verify where execution actually went inside the kernel:\n\n1. **Collect Coverage with `syz-execprog` and Symbolize with `addr2line`**:\n   Build `syz-execprog` (`CI=true .\u002Ftools\u002Fsyz-env make execprog`) and run the seed program inside\n   the VM with `-coverfile` (e.g., `syz-execprog -executor .\u002Fsyz-executor -coverfile \u002Ftmp\u002Fcover\n   -repeat 1 \u003Cseed_file>`) to dump the covered PCs for each call. Then pass the PCs from\n   `\u002Ftmp\u002Fcover` to `addr2line -f -e \u002Fpath\u002Fto\u002Fvmlinux` on the host to see the exact kernel functions\n   and source lines executed.\n2. **Enable Kernel `dynamic_debug` on the Console**:\n   Add `dyndbg=\"file *\u003Csubsystem>* +pflt\"` to `vm.cmdline` in the manager config and pass `-debug`\n   to `syz-manager` so kernel `pr_debug` \u002F `dev_dbg` state transitions are printed during the test\n   run.\n3. **Inspect Generated C Code (`syz-prog2c`)**:\n   As another debugging option, convert the seed program to standalone C with `.\u002Fbin\u002Fsyz-prog2c\n   -prog .\u002Fsys\u002Flinux\u002Ftest\u002F\u003Cseed_name> -trace` to inspect the exact memory offsets, struct layouts,\n   and setup calls (`setup_sysctl`, `initialize_netdevices_init`, etc.) or inspect `mmap` ring\n   state after a short `usleep`.\n4. **Clean Up**:\n   Remove temporary configs, workdirs, and downloaded artifacts in `\u002Ftmp\u002F` when done.\n","# Syzlang & Seed Program QEMU VM Verification\n\nUse this skill to verify new or updated Linux syscall descriptions (`sys\u002Flinux\u002F*.txt`), executor\nsetup (`executor\u002Fcommon_linux.h`), and seed programs (`sys\u002Flinux\u002Ftest\u002F*`) inside a QEMU VM.\n\nFor general syzlang description and seed authoring rules (and host-side parsing tests), see\n[`sys\u002FGEMINI.md`](..\u002F..\u002F..\u002Fsys\u002FGEMINI.md).\n\n## 1. Obtaining the VM Disk Image and Kernel\n\n1. **Userspace Disk Image (Buildroot)**:\n   If no disk image is available locally, download and decompress the standard syzkaller buildroot\n   image from `https:\u002F\u002Fstorage.googleapis.com\u002Fsyzkaller\u002Fimages\u002Fbuildroot-amd64-2025.05.gz`.\n\n2. **Kernel Image (`bzImage` and `vmlinux`)**:\n   - If the user provided a Linux kernel build directory or `bzImage` path, use it.\n   - Otherwise, visit `https:\u002F\u002Fsyzkaller.appspot.com\u002Fupstream\u002Fmanager\u002Fci-qemu-upstream`, download\n     the latest `kernel image` (`bzImage`) and `vmlinux` (if needed for coverage symbolization),\n     and decompress them.\n\n## 2. Running Seed Programs via `syz-manager -mode run-tests`\n\nBuild `syz-manager` and `syz-executor`:\n```bash\nCI=true .\u002Ftools\u002Fsyz-env make manager executor\n```\n\nCreate a minimal `syz-manager` config (e.g., `\u002Ftmp\u002Fruntest.cfg`):\n```json\n{\n\t\"name\": \"runtest\",\n\t\"target\": \"linux\u002Famd64\",\n\t\"http\": \"127.0.0.1:0\",\n\t\"workdir\": \"\u002Ftmp\u002Fsyz-runtest-workdir\",\n\t\"image\": \"\u002Ftmp\u002Fbuildroot-amd64.img\",\n\t\"syzkaller\": \".\",\n\t\"sandbox\": \"none\",\n\t\"procs\": 1,\n\t\"type\": \"qemu\",\n\t\"vm\": {\n\t\t\"count\": 1,\n\t\t\"kernel\": \"\u002Ftmp\u002FbzImage\",\n\t\t\"cmdline\": \"root=\u002Fdev\u002Fsda1\",\n\t\t\"cpu\": 2,\n\t\t\"mem\": 2048\n\t}\n}\n```\n- **KVM vs TCG**: By default on `linux\u002Famd64`, syzkaller passes\n  `-enable-kvm -cpu host,migratable=off` to QEMU. If KVM (`\u002Fdev\u002Fkvm`) is available on the host,\n  always use it. If KVM is not available, configure TCG in `vm.qemu_args` (e.g.,\n  `\"qemu_args\": \"-machine q35 -accel tcg -cpu max\"`) and be very patient, as booting an\n  instrumented kernel under software emulation takes several minutes.\n- **Sandbox**: If the seed program targets syscalls fuzzed under `\"sandbox\": \"namespace\"` in\n  production, also test with `\"sandbox\": \"namespace\"` to verify that devices or sockets created in\n  `init_net` work from child network namespaces.\n\nRun the specific seed test(s) with `-mode run-tests` and `-tests \u003Cprefix>`:\n```bash\n.\u002Fbin\u002Fsyz-manager -config \u002Ftmp\u002Fruntest.cfg -mode run-tests -tests \u003Cseed_name>\n```\n`syz-manager -mode run-tests` boots the QEMU VM, runs the machine check, and executes matching\n`sys\u002Flinux\u002Ftest\u002F\u003Cseed_name>` programs via both `syz-executor` (verifying KCOV coverage and that\nevery call returns the expected errno, `0` by default) and `pkg\u002Fcsource` C binaries. Pass `-debug`\nto dump full VM console and executor output.\n\n## 3. Debugging What the Program Actually Does in the Kernel\n\nA seed test passing with `errno=0` on every syscall is necessary, but for subsystems with\nasynchronous workqueues, tasklets, softirqs, or shared `mmap` rings (e.g., RDMA `rxe`, `io_uring`,\n`vhost`), the kicking syscall can return `0` even when the asynchronous worker immediately aborts\non a bad struct layout, ring offset, or key.\n\nWhen you need to verify where execution actually went inside the kernel:\n\n1. **Collect Coverage with `syz-execprog` and Symbolize with `addr2line`**:\n   Build `syz-execprog` (`CI=true .\u002Ftools\u002Fsyz-env make execprog`) and run the seed program inside\n   the VM with `-coverfile` (e.g., `syz-execprog -executor .\u002Fsyz-executor -coverfile \u002Ftmp\u002Fcover\n   -repeat 1 \u003Cseed_file>`) to dump the covered PCs for each call. Then pass the PCs from\n   `\u002Ftmp\u002Fcover` to `addr2line -f -e \u002Fpath\u002Fto\u002Fvmlinux` on the host to see the exact kernel functions\n   and source lines executed.\n2. **Enable Kernel `dynamic_debug` on the Console**:\n   Add `dyndbg=\"file *\u003Csubsystem>* +pflt\"` to `vm.cmdline` in the manager config and pass `-debug`\n   to `syz-manager` so kernel `pr_debug` \u002F `dev_dbg` state transitions are printed during the test\n   run.\n3. **Inspect Generated C Code (`syz-prog2c`)**:\n   As another debugging option, convert the seed program to standalone C with `.\u002Fbin\u002Fsyz-prog2c\n   -prog .\u002Fsys\u002Flinux\u002Ftest\u002F\u003Cseed_name> -trace` to inspect the exact memory offsets, struct layouts,\n   and setup calls (`setup_sysctl`, `initialize_netdevices_init`, etc.) or inspect `mmap` ring\n   state after a short `usleep`.\n4. **Clean Up**:\n   Remove temporary configs, workdirs, and downloaded artifacts in `\u002Ftmp\u002F` when done.\n",{"name":5,"description":7},"master","2041d3f83bef528d8be64c3fd1a5a54f35ef423b",".agents\u002Fskills\u002Fsyzlang-vm-testing",1473,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fsyzkaller","https:\u002F\u002Fgithub.com\u002Fgoogle","https:\u002F\u002Fopensource.google\u002F","Google ❤️ Open Source","2026-11-14 11:01:03",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add google\u002Fsyzkaller --skill syzlang-vm-testing",{"tool":59,"command":60},"bunx","bunx skills add google\u002Fsyzkaller --skill syzlang-vm-testing",{"tool":62,"command":63},"pnpm","pnpm dlx skills add google\u002Fsyzkaller --skill syzlang-vm-testing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fsyzkaller\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fsyzlang-vm-testing\u002FSKILL.md",true,[67],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Frun-button-bootstrap.md","REFERENCE","参考文档",4749,"https:\u002F\u002Fgithub.com\u002Filderaj\u002Fagent-plugin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fcodex--build-macos-apps\u002Fskills\u002Fbuild-run-debug\u002Freferences\u002Frun-button-bootstrap.md",[74,101],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":81,"publishedAt":39},"01M699651ENAPXQYYK9JKZ8HTS","linux-subsystems-update","Update and regenerate the Linux kernel subsystem list in pkg\u002Fsubsystem\u002Flists\u002Flinux.go (and custom rules in pkg\u002Fsubsystem\u002Flinux\u002F) using tools\u002Fsyz-query-subsystems against a mainline (torvalds) Linux kernel checkout. Use when regenerating Linux subsystems for a new kernel release, adding custom subsystem rules, fixing MAINTAINERS parsing\u002Fnaming errors, or associating syzkaller pseudo-syscalls with subsystems.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fsyzkaller\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Flinux-subsystems-update\u002FSKILL.md",[80],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[82,28,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,27,100],"linux subsystems update","update","query","new","release","Tools","parsing","Rules","list","use","checkout","maintainers","with","naming","errors","for","custom","when","go",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":39},"01M69962GK39RF8EK6612HZXAC","linux-config-update","Update Linux kernel configurations in dashboard\u002Fconfig\u002Flinux (bits\u002F*.yml, main.yml, and generated *.config files) using syz-kconf (`.\u002Ftools\u002Fsyz-env make configs`). Use when enabling or disabling kernel config options, bumping kernel tags (`bits\u002Flinux-upstream.yml`, `bits\u002Flinux-next.yml`), adding new config fragments or instances, or regenerating syzbot Linux kernel configs.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fsyzkaller\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Flinux-config-update\u002FSKILL.md",[],[28,83,108,109,27,110,111,87,112,91,113,114,115,116,117,118,119,120,99,85],"linux config update","config","options","dashboard","generated","files","instances","main","next","upstream","env","tags","make"]