[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699651ENAPXQYYK9JKZ8HTS":3,"skill-same:01M699651ENAPXQYYK9JKZ8HTS":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":45,"linkOnly":46,"markdownContent":47,"markdownBody":48,"frontMatter":49,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M699651ENAPXQYYK9JKZ8HTS","linux-subsystems-update",null,"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.","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\u002Flinux-subsystems-update\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,39,40,41,42,43,44],"linux","linux subsystems update","update","use","new","when","custom","for","errors","naming","with","maintainers","checkout","query","go","list","Rules","parsing","Tools","release","kernel","2026-11-10 10:12:30",false,"---\nname: linux-subsystems-update\ndescription: >-\n  Update and regenerate the Linux kernel subsystem list in pkg\u002Fsubsystem\u002Flists\u002Flinux.go\n  (and custom rules in pkg\u002Fsubsystem\u002Flinux\u002F) using tools\u002Fsyz-query-subsystems against a\n  mainline (torvalds) Linux kernel checkout. Use when regenerating Linux subsystems for a\n  new kernel release, adding custom subsystem rules, fixing MAINTAINERS parsing\u002Fnaming\n  errors, or associating syzkaller pseudo-syscalls with subsystems.\n---\n\n# Updating Linux Subsystems (`pkg\u002Fsubsystem\u002Flists\u002Flinux.go`)\n\nUse this skill when updating or regenerating [`pkg\u002Fsubsystem\u002Flists\u002Flinux.go`](..\u002F..\u002F..\u002Fpkg\u002Fsubsystem\u002Flists\u002Flinux.go)\nor modifying the Linux subsystem extraction rules in [`pkg\u002Fsubsystem\u002Flinux\u002F`](..\u002F..\u002F..\u002Fpkg\u002Fsubsystem\u002Flinux\u002F).\nRead the code in `pkg\u002Fsubsystem\u002Flinux\u002F` (`subsystems.go`, `rules.go`, `names.go`, `parents.go`, `maintainers.go`)\nas needed to understand how subsystems and hierarchies are inferred.\n\n## 1. Obtaining a Linux Kernel Checkout (`torvalds`, NOT `linux-next`)\n\nIf the user has not provided a path to a Linux kernel checkout (`$KERNEL_PATH`), **ask the user for one** before running the generator.\n\n> [!IMPORTANT]\n> - **Use upstream mainline (`torvalds\u002Flinux.git`), NOT `linux-next`.**\n>   All subsystem list updates target mainline Linux, ideally checked out at the latest release or\n>   release candidate tag (e.g., `v6.19-rc6`, `v6.16-rc7`) so the generated header comment and\n>   revision date reflect a mainline release tag.\n> - **Ensure the kernel working tree is clean.**\n>   The generator walks source files in `$KERNEL_PATH` to count files per subsystem and infer\n>   parent-child relationships. Untracked build artifacts or out-of-tree source files will skew file\n>   counts and parent inference.\n\n## 2. Running `syz-query-subsystems`\n\nNever hand-edit `pkg\u002Fsubsystem\u002Flists\u002Flinux.go`. Regenerate it via [`tools\u002Fsyz-query-subsystems`](..\u002F..\u002F..\u002Ftools\u002Fsyz-query-subsystems\u002Fquery_subsystems.go) (run directly on the host so `$KERNEL_PATH` outside the repo is accessible):\n\n```bash\ngo run .\u002Ftools\u002Fsyz-query-subsystems \\\n  -os linux \\\n  -kernel \"$KERNEL_PATH\" \\\n  -syzkaller . \\\n  -name linux\n```\n\n- Pass `-debug` to print the exact list of kernel source paths matched by each subsystem.\n- When investigating why a subsystem was dropped, merged, or assigned unexpected parents, it often helps to **apply temporary debugging changes** to [`pkg\u002Fsubsystem\u002Flinux\u002F`](..\u002F..\u002F..\u002Fpkg\u002Fsubsystem\u002Flinux\u002F) and re-run `syz-query-subsystems` to extract more information. Revert any temporary debugging code when done.\n\n## 3. Caveats & Resolving Regeneration Errors\n\nWhen `MAINTAINERS` or the kernel tree changes upstream, `syz-query-subsystems` may fail with errors or produce undesirable changes in `pkg\u002Fsubsystem\u002Flists\u002Flinux.go`:\n\n1. **Naming Failures or Collisions ([`pkg\u002Fsubsystem\u002Flinux\u002Fnames.go`](..\u002F..\u002F..\u002Fpkg\u002Fsubsystem\u002Flinux\u002Fnames.go))**:\n   - First check if the new mailing list actually represents a distinct kernel subsystem. If it is a secondary\u002Fuser list, a company\u002Fteam catch-all (`kernel@collabora.com`, `coreteam@netfilter.org`), or an overly broad cross-cutting list (`x86@kernel.org`), **exclude it** via `notSubsystemEmails` in [`pkg\u002Fsubsystem\u002Flinux\u002Frules.go`](..\u002F..\u002F..\u002Fpkg\u002Fsubsystem\u002Flinux\u002Frules.go).\n   - If it is a genuine subsystem whose mailing list cannot be cleanly parsed by the generic rules or produces a name longer than 16 characters, add a mapping to `emailExceptions` in `names.go` (and remove obsolete exceptions if a mailing list migrated upstream).\n\n2. **Broken or Dangling Custom Rules ([`pkg\u002Fsubsystem\u002Flinux\u002Frules.go`](..\u002F..\u002F..\u002Fpkg\u002Fsubsystem\u002Flinux\u002Frules.go))**:\n   - **`MAINTAINERS record not found`**: A section title in `extraSubsystems` was renamed or removed upstream in `MAINTAINERS`. Update `extraSubsystems` with the new title.\n   - **`unused keys` in rule checks**:\n     - If the subsystem was removed from the kernel (e.g., `bcachefs`, `reiserfs`), remove it from `rules.go` (if a `syz_mount_image$*` call still exists without a subsystem, move it to the `TODO` comment in `subsystemCalls`).\n     - If the subsystem was renamed or merged into another subsystem (e.g., `ntfs` -> `ntfs3`, `fat` -> `exfat`), move its rules to the new subsystem name.\n     - If a still-existing subsystem vanished only because its `L:` mailing list was removed or merged into a shared list (like `linux-fsdevel@vger.kernel.org` or `netdev@vger.kernel.org`), preserve it by adding its `MAINTAINERS` section title(s) to `extraSubsystems`.\n\n3. **`MAINTAINERS` Parser Issues ([`pkg\u002Fsubsystem\u002Flinux\u002Fmaintainers.go`](..\u002F..\u002F..\u002Fpkg\u002Fsubsystem\u002Flinux\u002Fmaintainers.go))**:\n   - Never edit `$KERNEL_PATH\u002FMAINTAINERS` to work around parsing errors. Fix the parser in `maintainers.go` and add a unit test in `maintainers_test.go`.\n\n## 4. Reviewing the Generated Diff in `pkg\u002Fsubsystem\u002Flists\u002Flinux.go`\n\nEven when `syz-query-subsystems` succeeds without errors, **always inspect the diff of `pkg\u002Fsubsystem\u002Flists\u002Flinux.go`**, especially the `\u002F\u002F The subsystem list:` hierarchy comment at the top:\n\n- **Overly Broad New Subsystems**: If a new mailing list covers a huge swath of the tree and swallows unrelated subsystems as children (check the `\u002F\u002F Auto-inferred:` parent comments), add the list to `notSubsystemEmails` in `rules.go`.\n- **Important Subsystems Lost**: If a major subsystem disappeared from the hierarchy tree because its dedicated mailing list was removed in `MAINTAINERS`, add it to `extraSubsystems` in `rules.go`.\n- **Custom Hierarchy Adjustments**: Use `addParents`, `noIndirectCc`, and `noReminders` in `rules.go` when automatic parent inference or CC rules need manual overrides.\n\n## 5. Testing and Committing\n\n1. **Run Subsystem and Dashboard Tests**:\n   ```bash\n   CI=true .\u002Ftools\u002Fsyz-env go test .\u002Fpkg\u002Fsubsystem\u002F... .\u002Fdashboard\u002Fapp\u002F...\n   ```\n   - If [`TestLinuxUpstreamSubsystems`](..\u002F..\u002F..\u002Fpkg\u002Fsubsystem\u002Flists\u002Flinux_test.go) fails after regeneration, investigate whether a subsystem's path rules or parent hierarchy regressed.\n\n2. **Commit Conventions**:\n   - Separate any parser\u002Flogic changes in `pkg\u002Fsubsystem\u002F` or `tools\u002Fsyz-query-subsystems\u002F` into their own commit(s) first.\n   - For the regeneration commit (including rule\u002Fname adjustments in `pkg\u002Fsubsystem\u002Flinux\u002F`), use a commit message like `pkg\u002Fsubsystem: regenerate Linux subsystems` and mention the target kernel tag (e.g., `v6.19-rc6`).\n","# Updating Linux Subsystems (`pkg\u002Fsubsystem\u002Flists\u002Flinux.go`)\n\nUse this skill when updating or regenerating [`pkg\u002Fsubsystem\u002Flists\u002Flinux.go`](..\u002F..\u002F..\u002Fpkg\u002Fsubsystem\u002Flists\u002Flinux.go)\nor modifying the Linux subsystem extraction rules in [`pkg\u002Fsubsystem\u002Flinux\u002F`](..\u002F..\u002F..\u002Fpkg\u002Fsubsystem\u002Flinux\u002F).\nRead the code in `pkg\u002Fsubsystem\u002Flinux\u002F` (`subsystems.go`, `rules.go`, `names.go`, `parents.go`, `maintainers.go`)\nas needed to understand how subsystems and hierarchies are inferred.\n\n## 1. Obtaining a Linux Kernel Checkout (`torvalds`, NOT `linux-next`)\n\nIf the user has not provided a path to a Linux kernel checkout (`$KERNEL_PATH`), **ask the user for one** before running the generator.\n\n> [!IMPORTANT]\n> - **Use upstream mainline (`torvalds\u002Flinux.git`), NOT `linux-next`.**\n>   All subsystem list updates target mainline Linux, ideally checked out at the latest release or\n>   release candidate tag (e.g., `v6.19-rc6`, `v6.16-rc7`) so the generated header comment and\n>   revision date reflect a mainline release tag.\n> - **Ensure the kernel working tree is clean.**\n>   The generator walks source files in `$KERNEL_PATH` to count files per subsystem and infer\n>   parent-child relationships. Untracked build artifacts or out-of-tree source files will skew file\n>   counts and parent inference.\n\n## 2. Running `syz-query-subsystems`\n\nNever hand-edit `pkg\u002Fsubsystem\u002Flists\u002Flinux.go`. Regenerate it via [`tools\u002Fsyz-query-subsystems`](..\u002F..\u002F..\u002Ftools\u002Fsyz-query-subsystems\u002Fquery_subsystems.go) (run directly on the host so `$KERNEL_PATH` outside the repo is accessible):\n\n```bash\ngo run .\u002Ftools\u002Fsyz-query-subsystems \\\n  -os linux \\\n  -kernel \"$KERNEL_PATH\" \\\n  -syzkaller . \\\n  -name linux\n```\n\n- Pass `-debug` to print the exact list of kernel source paths matched by each subsystem.\n- When investigating why a subsystem was dropped, merged, or assigned unexpected parents, it often helps to **apply temporary debugging changes** to [`pkg\u002Fsubsystem\u002Flinux\u002F`](..\u002F..\u002F..\u002Fpkg\u002Fsubsystem\u002Flinux\u002F) and re-run `syz-query-subsystems` to extract more information. Revert any temporary debugging code when done.\n\n## 3. Caveats & Resolving Regeneration Errors\n\nWhen `MAINTAINERS` or the kernel tree changes upstream, `syz-query-subsystems` may fail with errors or produce undesirable changes in `pkg\u002Fsubsystem\u002Flists\u002Flinux.go`:\n\n1. **Naming Failures or Collisions ([`pkg\u002Fsubsystem\u002Flinux\u002Fnames.go`](..\u002F..\u002F..\u002Fpkg\u002Fsubsystem\u002Flinux\u002Fnames.go))**:\n   - First check if the new mailing list actually represents a distinct kernel subsystem. If it is a secondary\u002Fuser list, a company\u002Fteam catch-all (`kernel@collabora.com`, `coreteam@netfilter.org`), or an overly broad cross-cutting list (`x86@kernel.org`), **exclude it** via `notSubsystemEmails` in [`pkg\u002Fsubsystem\u002Flinux\u002Frules.go`](..\u002F..\u002F..\u002Fpkg\u002Fsubsystem\u002Flinux\u002Frules.go).\n   - If it is a genuine subsystem whose mailing list cannot be cleanly parsed by the generic rules or produces a name longer than 16 characters, add a mapping to `emailExceptions` in `names.go` (and remove obsolete exceptions if a mailing list migrated upstream).\n\n2. **Broken or Dangling Custom Rules ([`pkg\u002Fsubsystem\u002Flinux\u002Frules.go`](..\u002F..\u002F..\u002Fpkg\u002Fsubsystem\u002Flinux\u002Frules.go))**:\n   - **`MAINTAINERS record not found`**: A section title in `extraSubsystems` was renamed or removed upstream in `MAINTAINERS`. Update `extraSubsystems` with the new title.\n   - **`unused keys` in rule checks**:\n     - If the subsystem was removed from the kernel (e.g., `bcachefs`, `reiserfs`), remove it from `rules.go` (if a `syz_mount_image$*` call still exists without a subsystem, move it to the `TODO` comment in `subsystemCalls`).\n     - If the subsystem was renamed or merged into another subsystem (e.g., `ntfs` -> `ntfs3`, `fat` -> `exfat`), move its rules to the new subsystem name.\n     - If a still-existing subsystem vanished only because its `L:` mailing list was removed or merged into a shared list (like `linux-fsdevel@vger.kernel.org` or `netdev@vger.kernel.org`), preserve it by adding its `MAINTAINERS` section title(s) to `extraSubsystems`.\n\n3. **`MAINTAINERS` Parser Issues ([`pkg\u002Fsubsystem\u002Flinux\u002Fmaintainers.go`](..\u002F..\u002F..\u002Fpkg\u002Fsubsystem\u002Flinux\u002Fmaintainers.go))**:\n   - Never edit `$KERNEL_PATH\u002FMAINTAINERS` to work around parsing errors. Fix the parser in `maintainers.go` and add a unit test in `maintainers_test.go`.\n\n## 4. Reviewing the Generated Diff in `pkg\u002Fsubsystem\u002Flists\u002Flinux.go`\n\nEven when `syz-query-subsystems` succeeds without errors, **always inspect the diff of `pkg\u002Fsubsystem\u002Flists\u002Flinux.go`**, especially the `\u002F\u002F The subsystem list:` hierarchy comment at the top:\n\n- **Overly Broad New Subsystems**: If a new mailing list covers a huge swath of the tree and swallows unrelated subsystems as children (check the `\u002F\u002F Auto-inferred:` parent comments), add the list to `notSubsystemEmails` in `rules.go`.\n- **Important Subsystems Lost**: If a major subsystem disappeared from the hierarchy tree because its dedicated mailing list was removed in `MAINTAINERS`, add it to `extraSubsystems` in `rules.go`.\n- **Custom Hierarchy Adjustments**: Use `addParents`, `noIndirectCc`, and `noReminders` in `rules.go` when automatic parent inference or CC rules need manual overrides.\n\n## 5. Testing and Committing\n\n1. **Run Subsystem and Dashboard Tests**:\n   ```bash\n   CI=true .\u002Ftools\u002Fsyz-env go test .\u002Fpkg\u002Fsubsystem\u002F... .\u002Fdashboard\u002Fapp\u002F...\n   ```\n   - If [`TestLinuxUpstreamSubsystems`](..\u002F..\u002F..\u002Fpkg\u002Fsubsystem\u002Flists\u002Flinux_test.go) fails after regeneration, investigate whether a subsystem's path rules or parent hierarchy regressed.\n\n2. **Commit Conventions**:\n   - Separate any parser\u002Flogic changes in `pkg\u002Fsubsystem\u002F` or `tools\u002Fsyz-query-subsystems\u002F` into their own commit(s) first.\n   - For the regeneration commit (including rule\u002Fname adjustments in `pkg\u002Fsubsystem\u002Flinux\u002F`), use a commit message like `pkg\u002Fsubsystem: regenerate Linux subsystems` and mention the target kernel tag (e.g., `v6.19-rc6`).\n",{"name":5,"description":7},"master","5af5b6c697a1738ab85e5fc04286092dbcdcedb5",".agents\u002Fskills\u002Flinux-subsystems-update",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":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add google\u002Fsyzkaller --skill linux-subsystems-update",{"tool":65,"command":66},"bunx","bunx skills add google\u002Fsyzkaller --skill linux-subsystems-update",{"tool":68,"command":69},"pnpm","pnpm dlx skills add google\u002Fsyzkaller --skill linux-subsystems-update","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fsyzkaller\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Flinux-subsystems-update\u002FSKILL.md",true,[],[74,95],{"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":45},"01M699670CJEK1464D5PCED8MV","syzlang-vm-testing","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.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fsyzkaller\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fsyzlang-vm-testing\u002FSKILL.md",[80],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[82,83,84,85,86,87,88,89,90,91,92,93,24,44,94],"testing","syzlang vm testing","vm","mode","tests","seed","images","verify","tracing","run","debug","test","manager",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":45},"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",[],[24,26,102,103,44,28,29,104,105,106,107,108,109,110,111,112,27,113,42,114],"config","linux config update","make","tags","env","upstream","options","next","main","instances","files","generated","dashboard"]