[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69962GK39RF8EK6612HZXAC":3,"skill-same:01M69962GK39RF8EK6612HZXAC":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":18,"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},"01M69962GK39RF8EK6612HZXAC","linux-config-update",null,"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.","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-config-update\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"linux","linux config update","config","update","new","kernel","when","make","tags","env","upstream","options","next","main","instances","files","use","generated","Tools","dashboard","2026-11-10 10:12:30",false,"---\nname: linux-config-update\ndescription: >-\n  Update Linux kernel configurations in dashboard\u002Fconfig\u002Flinux (bits\u002F*.yml, main.yml, and\n  generated *.config files) using syz-kconf (`.\u002Ftools\u002Fsyz-env make configs`). Use when enabling or\n  disabling kernel config options, bumping kernel tags (`bits\u002Flinux-upstream.yml`, `bits\u002Flinux-next.yml`),\n  adding new config fragments or instances, or regenerating syzbot Linux kernel configs.\n---\n\n# Updating Linux Kernel Configs (`dashboard\u002Fconfig\u002Flinux`)\n\nUse this skill when modifying `dashboard\u002Fconfig\u002Flinux\u002F` — whether enabling new `CONFIG_*` options,\nupdating kernel tags for a new Linux release, adding new instances\u002Ffragments, or regenerating\n`.config` files.\n\nFirst, read [`dashboard\u002Fconfig\u002Flinux\u002FREADME.md`](..\u002F..\u002F..\u002Fdashboard\u002Fconfig\u002Flinux\u002FREADME.md) for the\n`main.yml` and `bits\u002F*.yml` declarative syntax, instance features (`baseline`, `base-config`,\n`nonoise`, `reduced`, `vX.Y` version tags), and how [`tools\u002Fsyz-kconf`](..\u002F..\u002F..\u002Ftools\u002Fsyz-kconf\u002Fkconf.go)\ngenerates `\u003Cname>.config` and `\u003Cname>-base.config`.\n\n## 1. Running `make configs` (Always Use `syz-env`!)\n\n> [!IMPORTANT]\n> **Always run config generation inside `.\u002Ftools\u002Fsyz-env`.**\n> Kernel Kconfig evaluates compiler capabilities (`cc-option`, `CC_VERSION_TEXT`, `CLANG_VERSION`,\n> `GCC_VERSION`, rustc\u002Fbindgen availability, etc.). Running outside `syz-env` uses host compilers\n> and produces massive, unintended diffs across all `.config` files.\n> **Never manually edit generated `*.config` files.**\n\n### Fast Iteration with `INSTANCE=`\n\nA full `make configs` run checks out multiple kernel trees (upstream, linux-next, stable, Android,\nChromeOS) and generates ~80 configs, which is very slow.\n\nWhen testing new options or debugging a failure, iterate on individual instances first using\n`INSTANCE=\u003Cname>` (or `INSTANCE=\u003Cname>-base` for the baseline config):\n\n```bash\n# Quick check on a single upstream x86_64 instance:\nCI=true .\u002Ftools\u002Fsyz-env make configs SOURCEDIR=$KERNEL_PATH INSTANCE=upstream-apparmor-kasan\n\n# Check older stable\u002Fandroid\u002Farch\u002Fsanitizer instances to verify version and arch constraints:\nCI=true .\u002Ftools\u002Fsyz-env make configs SOURCEDIR=$KERNEL_PATH INSTANCE=stable-5.15-kasan\nCI=true .\u002Ftools\u002Fsyz-env make configs SOURCEDIR=$KERNEL_PATH INSTANCE=upstream-s390-kasan\nCI=true .\u002Ftools\u002Fsyz-env make configs SOURCEDIR=$KERNEL_PATH INSTANCE=upstream-kmsan\n```\n\nOnce single-instance checks pass, run the **full** command without `INSTANCE=` to update all\naffected `.config` files before committing:\n```bash\nCI=true .\u002Ftools\u002Fsyz-env make configs SOURCEDIR=$KERNEL_PATH\n```\nRemove any untracked `dashboard\u002Fconfig\u002Flinux\u002F*.config.tmp` files if left behind.\n\n## 2. Determining Kernel Versions for New or Removed Options\n\nNever guess version constraints or slap `weak` \u002F `optional` on a config to silence errors on older\nkernels. Always find the exact kernel release in `$KERNEL_PATH`:\n\n1. **Find When a New Option Appeared**:\n   ```bash\n   # Find the commit that introduced `config FOO` in Kconfig:\n   git -C \"$KERNEL_PATH\" log -S \"config FOO\" --oneline -- \"**\u002FKconfig*\" \"Kconfig*\"\n\n   # Instant check of the base kernel version at that commit:\n   git -C \"$KERNEL_PATH\" show \u003Ccommit_hash>:Makefile | head -n 5\n\n   # Verify the exact release tag containing that commit (note: a commit authored on v6.13-rcX\n   # typically merges in v6.14-rc1):\n   git -C \"$KERNEL_PATH\" merge-base --is-ancestor \u003Ccommit_hash> v6.14\n   # Or:\n   git -C \"$KERNEL_PATH\" describe --contains --match \"v[0-9]*.[0-9]*-rc1\" \u003Ccommit_hash>\n   # e.g., \"v6.14-rc1~42^2~5\" -> appeared in v6.14 -> use [v6.14]\n   ```\n   - If the oldest kernel instance that includes the fragment already has the option (note:\n     `android-5.4` is `v5.4`, `android-5.10` \u002F `chromeos-5.10` are `v5.10`, `stable-5.15` is\n     `v5.15`), no version tag is needed.\n   - If the commit is only in `linux-next` and not yet in `bits\u002Flinux-upstream.yml`, use\n     `[linux-next]`. When bumping `bits\u002Flinux-upstream.yml` to a new release, replace `[linux-next]`\n     on options that graduated into mainline with their `[vX.Y]` tag.\n   - Inspect `depends on` in the Kconfig definition: if `FOO` depends on an architecture (e.g.,\n     `X86_64`) or conflicts with a feature (e.g., `!PREEMPT_RT`, `!KMSAN`), add the corresponding\n     constraints (e.g., `[x86_64, v6.14]`, `[-s390]`, `[-preempt_rt]`).\n\n2. **Find When an Option Was Removed, Renamed, or Migrated**:\n   ```bash\n   git -C \"$KERNEL_PATH\" log -n 5 -S \"config OLD_FOO\" --oneline -- \"**\u002FKconfig*\" \"Kconfig*\"\n   git -C \"$KERNEL_PATH\" describe --contains --match \"v[0-9]*.[0-9]*-rc1\" \u003Ccommit_hash>\n   ```\n   - Add an upper-bound version constraint (e.g., `[-v7.1]`) and document the kernel commit above it:\n     - `# Removed in \u003C12-char-hash> \"\u003Ccommit_title>\".`\n     - `# Renamed to \u003CNEW_CONFIG> in \u003C12-char-hash> \"\u003Ccommit_title>\".` (and add `- NEW_CONFIG: [vX.Y]`)\n     - `# Migrated to library in \u003C12-char-hash> \"\u003Ccommit_title>\".`\n   - If the option was only tagged `[linux-next]` (never enabled in any released kernel config),\n     remove the line directly and explain it in the commit message.\n\n## 3. Avoid `override`, `weak`, and `optional` at All Costs\n\n> [!WARNING]\n> **Avoid `override`, `weak`, and `optional` at all costs!**\n> They hide broken dependencies, silently drop coverage when Kconfig dependencies change in future\n> kernel releases, and make fragment inclusion order fragile.\n\nUse these patterns instead:\n\n1. **Instead of `weak` \u002F `optional` when an option fails verification on some instances**:\n   - Inspect why `olddefconfig` dropped or altered the option (check Kconfig `depends on` and\n     `select` in `$KERNEL_PATH`, and compare `\u003Cinstance>.config.tmp` with `\u003Cinstance>.config`).\n   - Enable missing prerequisite Kconfig options if appropriate.\n   - Otherwise, add **explicit constraints** for the kernel version, architecture, or instance\n     features where the option is unsupported (e.g., `[v6.17, x86_64, -kmsan, -preempt_rt]`,\n     `[-arm, -riscv, -s390]`), with a brief comment explaining non-obvious exclusions.\n\n2. **Instead of `override` when two fragments or features want different values**:\n   - **Use mutual exclusion tags on the original definition**: For example, when enabling\n     `ANDROID_BINDER_IPC_RUST: [v6.18, rust]`, do NOT override `ANDROID_BINDER_IPC: n` in `rust.yml`.\n     Instead, restrict the original entry in `subsystems.yml` to `ANDROID_BINDER_IPC: [-rust]`.\n   - **Move the option to a more specific existing bit or extract a new `bits\u002F\u003Ctopic>.yml` bit**:\n     - Example: `DEBUG_INFO_BTF` was moved from `base.yml` to `bpf.yml` (which is excluded on\n       `-baseline`, `-onlynet`, `-onlyusb`) instead of overriding it in baseline\u002Fminimal configs.\n     - Example: Sound options were extracted from `subsystems.yml` into `bits\u002Fsound.yml` included in\n       `main.yml` with `[-baseline, -onlynet, -onlyusb, -arm64_gce]`.\n     - Every new file created in `dashboard\u002Fconfig\u002Flinux\u002Fbits\u002F` must have a copyright header and a\n       top-level comment explaining the purpose of the fragment and where it is used.\n\n3. **When all options in a fragment are removed in a new kernel**:\n   - Exclude the entire fragment in `main.yml` using instance tags (e.g., `-upstream, -linux-next`\n     with a comment citing the removal commit, as done for `hamradio.yml`; remember `[-vX.Y]` does\n     not work on `includes:` in `main.yml`).\n\n## 4. Troubleshooting Common Issues\n\n- **`pkg\u002Fkconfig` Parser Limitations**:\n  If a new kernel introduces Kconfig syntax that `syz-kconf` fails to parse, **never modify Kconfig\n  files in `$KERNEL_PATH`**. Implement support for the syntax in\n  [`pkg\u002Fkconfig\u002Fkconfig.go`](..\u002F..\u002F..\u002Fpkg\u002Fkconfig\u002Fkconfig.go) and add a test in\n  [`pkg\u002Fkconfig\u002Fkconfig_test.go`](..\u002F..\u002F..\u002Fpkg\u002Fkconfig\u002Fkconfig_test.go).\n- **Git Fetch \u002F Checkout Failures**:\n  `syz-kconf` adds hashed remotes to `$KERNEL_PATH`. If a checkout fails (e.g., on Android\u002FChromeOS\n  trees), find the remote hash in the error output, run `git -C \"$KERNEL_PATH\" fetch \u003Cremote> \u003Ctag>`\n  manually, and retry `make configs`.\n\n## 5. Commit Structure & Conventions\n\n- When updating `bits\u002Flinux-upstream.yml` and `bits\u002Flinux-next.yml` to new tags (use release tags\n  like `v7.2` or `next-YYYYMMDD`, not raw commit hashes), split changes into logical commits:\n  1. `dashboard\u002Fconfig\u002Flinux: update config fragments for vX.Y` (tag updates + disabling removed\n     options with commit references).\n  2. `dashboard\u002Fconfig\u002Flinux: enable more configs` (enabling newly introduced bug-finding or\n     subsystem options; if notable new options were skipped, explain why in the commit message).\n  3. `dashboard\u002Fconfig\u002Flinux: update generated configs` (the generated `*.config` files as the\n     very last commit).\n- For targeted single-feature changes (e.g., `dashboard\u002Fconfig\u002Flinux: enable CONFIG_FOO`), check\n  whether the user wants a single commit or separate commits for `bits\u002F` and `*.config`.\n","# Updating Linux Kernel Configs (`dashboard\u002Fconfig\u002Flinux`)\n\nUse this skill when modifying `dashboard\u002Fconfig\u002Flinux\u002F` — whether enabling new `CONFIG_*` options,\nupdating kernel tags for a new Linux release, adding new instances\u002Ffragments, or regenerating\n`.config` files.\n\nFirst, read [`dashboard\u002Fconfig\u002Flinux\u002FREADME.md`](..\u002F..\u002F..\u002Fdashboard\u002Fconfig\u002Flinux\u002FREADME.md) for the\n`main.yml` and `bits\u002F*.yml` declarative syntax, instance features (`baseline`, `base-config`,\n`nonoise`, `reduced`, `vX.Y` version tags), and how [`tools\u002Fsyz-kconf`](..\u002F..\u002F..\u002Ftools\u002Fsyz-kconf\u002Fkconf.go)\ngenerates `\u003Cname>.config` and `\u003Cname>-base.config`.\n\n## 1. Running `make configs` (Always Use `syz-env`!)\n\n> [!IMPORTANT]\n> **Always run config generation inside `.\u002Ftools\u002Fsyz-env`.**\n> Kernel Kconfig evaluates compiler capabilities (`cc-option`, `CC_VERSION_TEXT`, `CLANG_VERSION`,\n> `GCC_VERSION`, rustc\u002Fbindgen availability, etc.). Running outside `syz-env` uses host compilers\n> and produces massive, unintended diffs across all `.config` files.\n> **Never manually edit generated `*.config` files.**\n\n### Fast Iteration with `INSTANCE=`\n\nA full `make configs` run checks out multiple kernel trees (upstream, linux-next, stable, Android,\nChromeOS) and generates ~80 configs, which is very slow.\n\nWhen testing new options or debugging a failure, iterate on individual instances first using\n`INSTANCE=\u003Cname>` (or `INSTANCE=\u003Cname>-base` for the baseline config):\n\n```bash\n# Quick check on a single upstream x86_64 instance:\nCI=true .\u002Ftools\u002Fsyz-env make configs SOURCEDIR=$KERNEL_PATH INSTANCE=upstream-apparmor-kasan\n\n# Check older stable\u002Fandroid\u002Farch\u002Fsanitizer instances to verify version and arch constraints:\nCI=true .\u002Ftools\u002Fsyz-env make configs SOURCEDIR=$KERNEL_PATH INSTANCE=stable-5.15-kasan\nCI=true .\u002Ftools\u002Fsyz-env make configs SOURCEDIR=$KERNEL_PATH INSTANCE=upstream-s390-kasan\nCI=true .\u002Ftools\u002Fsyz-env make configs SOURCEDIR=$KERNEL_PATH INSTANCE=upstream-kmsan\n```\n\nOnce single-instance checks pass, run the **full** command without `INSTANCE=` to update all\naffected `.config` files before committing:\n```bash\nCI=true .\u002Ftools\u002Fsyz-env make configs SOURCEDIR=$KERNEL_PATH\n```\nRemove any untracked `dashboard\u002Fconfig\u002Flinux\u002F*.config.tmp` files if left behind.\n\n## 2. Determining Kernel Versions for New or Removed Options\n\nNever guess version constraints or slap `weak` \u002F `optional` on a config to silence errors on older\nkernels. Always find the exact kernel release in `$KERNEL_PATH`:\n\n1. **Find When a New Option Appeared**:\n   ```bash\n   # Find the commit that introduced `config FOO` in Kconfig:\n   git -C \"$KERNEL_PATH\" log -S \"config FOO\" --oneline -- \"**\u002FKconfig*\" \"Kconfig*\"\n\n   # Instant check of the base kernel version at that commit:\n   git -C \"$KERNEL_PATH\" show \u003Ccommit_hash>:Makefile | head -n 5\n\n   # Verify the exact release tag containing that commit (note: a commit authored on v6.13-rcX\n   # typically merges in v6.14-rc1):\n   git -C \"$KERNEL_PATH\" merge-base --is-ancestor \u003Ccommit_hash> v6.14\n   # Or:\n   git -C \"$KERNEL_PATH\" describe --contains --match \"v[0-9]*.[0-9]*-rc1\" \u003Ccommit_hash>\n   # e.g., \"v6.14-rc1~42^2~5\" -> appeared in v6.14 -> use [v6.14]\n   ```\n   - If the oldest kernel instance that includes the fragment already has the option (note:\n     `android-5.4` is `v5.4`, `android-5.10` \u002F `chromeos-5.10` are `v5.10`, `stable-5.15` is\n     `v5.15`), no version tag is needed.\n   - If the commit is only in `linux-next` and not yet in `bits\u002Flinux-upstream.yml`, use\n     `[linux-next]`. When bumping `bits\u002Flinux-upstream.yml` to a new release, replace `[linux-next]`\n     on options that graduated into mainline with their `[vX.Y]` tag.\n   - Inspect `depends on` in the Kconfig definition: if `FOO` depends on an architecture (e.g.,\n     `X86_64`) or conflicts with a feature (e.g., `!PREEMPT_RT`, `!KMSAN`), add the corresponding\n     constraints (e.g., `[x86_64, v6.14]`, `[-s390]`, `[-preempt_rt]`).\n\n2. **Find When an Option Was Removed, Renamed, or Migrated**:\n   ```bash\n   git -C \"$KERNEL_PATH\" log -n 5 -S \"config OLD_FOO\" --oneline -- \"**\u002FKconfig*\" \"Kconfig*\"\n   git -C \"$KERNEL_PATH\" describe --contains --match \"v[0-9]*.[0-9]*-rc1\" \u003Ccommit_hash>\n   ```\n   - Add an upper-bound version constraint (e.g., `[-v7.1]`) and document the kernel commit above it:\n     - `# Removed in \u003C12-char-hash> \"\u003Ccommit_title>\".`\n     - `# Renamed to \u003CNEW_CONFIG> in \u003C12-char-hash> \"\u003Ccommit_title>\".` (and add `- NEW_CONFIG: [vX.Y]`)\n     - `# Migrated to library in \u003C12-char-hash> \"\u003Ccommit_title>\".`\n   - If the option was only tagged `[linux-next]` (never enabled in any released kernel config),\n     remove the line directly and explain it in the commit message.\n\n## 3. Avoid `override`, `weak`, and `optional` at All Costs\n\n> [!WARNING]\n> **Avoid `override`, `weak`, and `optional` at all costs!**\n> They hide broken dependencies, silently drop coverage when Kconfig dependencies change in future\n> kernel releases, and make fragment inclusion order fragile.\n\nUse these patterns instead:\n\n1. **Instead of `weak` \u002F `optional` when an option fails verification on some instances**:\n   - Inspect why `olddefconfig` dropped or altered the option (check Kconfig `depends on` and\n     `select` in `$KERNEL_PATH`, and compare `\u003Cinstance>.config.tmp` with `\u003Cinstance>.config`).\n   - Enable missing prerequisite Kconfig options if appropriate.\n   - Otherwise, add **explicit constraints** for the kernel version, architecture, or instance\n     features where the option is unsupported (e.g., `[v6.17, x86_64, -kmsan, -preempt_rt]`,\n     `[-arm, -riscv, -s390]`), with a brief comment explaining non-obvious exclusions.\n\n2. **Instead of `override` when two fragments or features want different values**:\n   - **Use mutual exclusion tags on the original definition**: For example, when enabling\n     `ANDROID_BINDER_IPC_RUST: [v6.18, rust]`, do NOT override `ANDROID_BINDER_IPC: n` in `rust.yml`.\n     Instead, restrict the original entry in `subsystems.yml` to `ANDROID_BINDER_IPC: [-rust]`.\n   - **Move the option to a more specific existing bit or extract a new `bits\u002F\u003Ctopic>.yml` bit**:\n     - Example: `DEBUG_INFO_BTF` was moved from `base.yml` to `bpf.yml` (which is excluded on\n       `-baseline`, `-onlynet`, `-onlyusb`) instead of overriding it in baseline\u002Fminimal configs.\n     - Example: Sound options were extracted from `subsystems.yml` into `bits\u002Fsound.yml` included in\n       `main.yml` with `[-baseline, -onlynet, -onlyusb, -arm64_gce]`.\n     - Every new file created in `dashboard\u002Fconfig\u002Flinux\u002Fbits\u002F` must have a copyright header and a\n       top-level comment explaining the purpose of the fragment and where it is used.\n\n3. **When all options in a fragment are removed in a new kernel**:\n   - Exclude the entire fragment in `main.yml` using instance tags (e.g., `-upstream, -linux-next`\n     with a comment citing the removal commit, as done for `hamradio.yml`; remember `[-vX.Y]` does\n     not work on `includes:` in `main.yml`).\n\n## 4. Troubleshooting Common Issues\n\n- **`pkg\u002Fkconfig` Parser Limitations**:\n  If a new kernel introduces Kconfig syntax that `syz-kconf` fails to parse, **never modify Kconfig\n  files in `$KERNEL_PATH`**. Implement support for the syntax in\n  [`pkg\u002Fkconfig\u002Fkconfig.go`](..\u002F..\u002F..\u002Fpkg\u002Fkconfig\u002Fkconfig.go) and add a test in\n  [`pkg\u002Fkconfig\u002Fkconfig_test.go`](..\u002F..\u002F..\u002Fpkg\u002Fkconfig\u002Fkconfig_test.go).\n- **Git Fetch \u002F Checkout Failures**:\n  `syz-kconf` adds hashed remotes to `$KERNEL_PATH`. If a checkout fails (e.g., on Android\u002FChromeOS\n  trees), find the remote hash in the error output, run `git -C \"$KERNEL_PATH\" fetch \u003Cremote> \u003Ctag>`\n  manually, and retry `make configs`.\n\n## 5. Commit Structure & Conventions\n\n- When updating `bits\u002Flinux-upstream.yml` and `bits\u002Flinux-next.yml` to new tags (use release tags\n  like `v7.2` or `next-YYYYMMDD`, not raw commit hashes), split changes into logical commits:\n  1. `dashboard\u002Fconfig\u002Flinux: update config fragments for vX.Y` (tag updates + disabling removed\n     options with commit references).\n  2. `dashboard\u002Fconfig\u002Flinux: enable more configs` (enabling newly introduced bug-finding or\n     subsystem options; if notable new options were skipped, explain why in the commit message).\n  3. `dashboard\u002Fconfig\u002Flinux: update generated configs` (the generated `*.config` files as the\n     very last commit).\n- For targeted single-feature changes (e.g., `dashboard\u002Fconfig\u002Flinux: enable CONFIG_FOO`), check\n  whether the user wants a single commit or separate commits for `bits\u002F` and `*.config`.\n",{"name":5,"description":7},"master","2041d3f83bef528d8be64c3fd1a5a54f35ef423b",".agents\u002Fskills\u002Flinux-config-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":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add google\u002Fsyzkaller --skill linux-config-update",{"tool":59,"command":60},"bunx","bunx skills add google\u002Fsyzkaller --skill linux-config-update",{"tool":62,"command":63},"pnpm","pnpm dlx skills add google\u002Fsyzkaller --skill linux-config-update","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fsyzkaller\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Flinux-config-update\u002FSKILL.md",true,[67],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fliquid-glass.md","REFERENCE","参考文档",8159,"https:\u002F\u002Fgithub.com\u002Filderaj\u002Fagent-plugin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fcodex--build-ios-apps\u002Fskills\u002Fswiftui-liquid-glass\u002Freferences\u002Fliquid-glass.md",[74,99],{"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":85,"publishedAt":39},"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":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[86,87,88,89,24,19,90,91,92,93,94,95,96,97,98],"testing","syzlang vm testing","vm","tracing","test","debug","run","verify","images","seed","tests","mode","manager",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":106,"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",[105],{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},[19,107,22,23,108,25,109,110,111,112,113,114,115,116,35,117,118,119,37,120,24],"linux subsystems update","custom","go","for","errors","naming","with","maintainers","checkout","query","list","Rules","parsing","release"]