Syzkaller Ppdev Syzlang logo

Syzkaller Ppdev Syzlang

Community
Zhang-Henry
syzkaller-ppdev-syzlang

Write syzkaller syzlang system call descriptions for the Linux ppdev (parallel port) driver. Use when creating .txt and .txt.const files for fuzzing /dev/parportN devices, describing ppdev ioctls, resources, structs, flags, and computing ioctl command numbers.

Overview

PublisherZhang-Henry
RepositoryCoEvoSkills
Skill namesyzkaller-ppdev-syzlang
Stars
83
Forks
9
Bundled files
Instructions only
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by Zhang-Henry on GitHub. Read the source before you install it.

Installation

Install the Syzkaller Ppdev Syzlang AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Zhang-Henry/CoEvoSkills/tree/main/artifacts/skills/syzkaller-ppdev-syzlang/syzkaller-ppdev-syzlang
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Zhang-Henry/CoEvoSkills.git /tmp/CoEvoSkills
mkdir -p .claude/skills
cp -r /tmp/CoEvoSkills/artifacts/skills/syzkaller-ppdev-syzlang/syzkaller-ppdev-syzlang .claude/skills/syzkaller-ppdev-syzlang
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Syzkaller Ppdev Syzlang in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Syzkaller Ppdev Syzlang on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Syzkaller Ppdev Syzlang is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Syzkaller Syzlang Descriptions for ppdev

This skill produces two files for the syzkaller kernel fuzzer:

  1. A .txt syzlang description file for the ppdev driver
  2. A .txt.const constants file with architecture-specific numeric values

File Structure

The .txt file follows this order:

  1. Include directives
  2. Resource declarations
  3. Device open call
  4. Ioctl descriptions
  5. Struct definitions
  6. Flag definitions

Include Directives

Start with the kernel headers that define ppdev and parport constants:

include <linux/ppdev.h>
include <linux/parport.h>

Resource Declaration

Declare a file descriptor resource for ppdev devices:

resource fd_ppdev[fd]

Device Opening

Use syz_open_dev with the parport device path template. The # is replaced by syzkaller with small integers during fuzzing:

syz_open_dev$ppdev(dev ptr[in, string["/dev/parport#"]], id intptr, flags flags[open_flags]) fd_ppdev

Ioctl Descriptions

Each ioctl specializes the generic ioctl syscall with a $NAME suffix.

No-data ioctls (use _IO encoding)

These take exactly two parameters - fd and command constant. No third argument:

ioctl$PPCLAIM(fd fd_ppdev, cmd const[PPCLAIM])
ioctl$PPRELEASE(fd fd_ppdev, cmd const[PPRELEASE])
ioctl$PPYIELD(fd fd_ppdev, cmd const[PPYIELD])
ioctl$PPEXCL(fd fd_ppdev, cmd const[PPEXCL])

Data-transferring ioctls

These add a third ptr[direction, type] argument.

Direction mapping (this is critical to get right):

  • _IOW (user writes TO kernel) → ptr[in, ...]
  • _IOR (kernel reads OUT to user) → ptr[out, ...]

Mode management (4-byte int):

ioctl$PPSETMODE(fd fd_ppdev, cmd const[PPSETMODE], arg ptr[in, flags[ieee1284_modes, int32]])
ioctl$PPGETMODE(fd fd_ppdev, cmd const[PPGETMODE], arg ptr[out, int32])
ioctl$PPGETMODES(fd fd_ppdev, cmd const[PPGETMODES], arg ptr[out, int32])
ioctl$PPNEGOT(fd fd_ppdev, cmd const[PPNEGOT], arg ptr[in, flags[ieee1284_modes, int32]])

Data transfer (1-byte):

ioctl$PPRDATA(fd fd_ppdev, cmd const[PPRDATA], arg ptr[out, int8])
ioctl$PPWDATA(fd fd_ppdev, cmd const[PPWDATA], arg ptr[in, int8])
ioctl$PPDATADIR(fd fd_ppdev, cmd const[PPDATADIR], arg ptr[in, int32])

Status and control:

ioctl$PPRSTATUS(fd fd_ppdev, cmd const[PPRSTATUS], arg ptr[out, int8])
ioctl$PPRCONTROL(fd fd_ppdev, cmd const[PPRCONTROL], arg ptr[out, int8])
ioctl$PPWCONTROL(fd fd_ppdev, cmd const[PPWCONTROL], arg ptr[in, int8])
ioctl$PPFCONTROL(fd fd_ppdev, cmd const[PPFCONTROL], arg ptr[in, ppdev_frob_struct])
ioctl$PPWCTLONIRQ(fd fd_ppdev, cmd const[PPWCTLONIRQ], arg ptr[in, int8])

IRQ and timing:

ioctl$PPCLRIRQ(fd fd_ppdev, cmd const[PPCLRIRQ], arg ptr[out, int32])
ioctl$PPGETTIME(fd fd_ppdev, cmd const[PPGETTIME], arg ptr[out, timeval])
ioctl$PPSETTIME(fd fd_ppdev, cmd const[PPSETTIME], arg ptr[in, timeval])

Flags and phase (4-byte int):

ioctl$PPGETFLAGS(fd fd_ppdev, cmd const[PPGETFLAGS], arg ptr[out, int32])
ioctl$PPSETFLAGS(fd fd_ppdev, cmd const[PPSETFLAGS], arg ptr[in, flags[ppdev_flags, int32]])
ioctl$PPGETPHASE(fd fd_ppdev, cmd const[PPGETPHASE], arg ptr[out, int32])
ioctl$PPSETPHASE(fd fd_ppdev, cmd const[PPSETPHASE], arg ptr[in, int32])

Struct Definitions

ppdev_frob_struct {
	mask	int8
	val	int8
}

The frob struct is exactly 2 bytes (two unsigned char fields). Using wrong sizes changes the ioctl number.

Flag Definitions

ieee1284_modes = IEEE1284_MODE_NIBBLE, IEEE1284_MODE_BYTE, IEEE1284_MODE_COMPAT, IEEE1284_MODE_ECP, IEEE1284_MODE_ECPRLE, IEEE1284_MODE_ECPSWE, IEEE1284_MODE_EPP, IEEE1284_MODE_EPPSWE, IEEE1284_DEVICEID, IEEE1284_EXT_LINK
ppdev_flags = PP_FASTWRITE, PP_FASTREAD, PP_W91284PIC

Computing Ioctl Numbers for .txt.const

All ppdev ioctls use type character 'p' (ASCII 0x70 = 112).

Encoding formula

MacroFormula
_IO(type, nr)(type << 8) | nr
_IOR(type, nr, size)0x80000000 | (size << 16) | (type << 8) | nr
_IOW(type, nr, size)0x40000000 | (size << 16) | (type << 8) | nr

Data type sizes: int=4, char/unsigned char=1, ppdev_frob_struct=2, timeval=16 (on 64-bit)

Example: PPSETMODE = _IOW('p', 0x80, int)

0x40000000 | (4 << 16) | (0x70 << 8) | 0x80 = 0x40047080 = 1074032768

Constants File Format

The .txt.const file must:

  • Start with arches = amd64, 386 (or appropriate architectures)
  • List every symbolic constant from the .txt file
  • Use decimal values (not hex)
  • Include ioctl command numbers, flag values, and all other constants

A missing constant causes syz-sysgen compilation failure.

Common Pitfalls

  1. Direction confusion: _IOR → ptr[out, ...], _IOW → ptr[in, ...]. The R/W is from kernel perspective.
  2. Wrong data sizes: Each ioctl encodes its argument size. int=4 bytes, char=1 byte, frob=2 bytes, timeval=16 bytes.
  3. Hex in const file: Values must be decimal. 0x40047080 is wrong; 1074032768 is correct.
  4. Missing arches line: The const file needs arches = amd64, 386.
  5. No-data ioctls with extra args: _IO ioctls (PPCLAIM, PPRELEASE, PPYIELD, PPEXCL) must NOT have a third pointer argument.
  6. Missing constants: Every symbol in .txt needs an entry in .txt.const.

Frequently asked questions

What does the Syzkaller Ppdev Syzlang AI skill do?

Write syzkaller syzlang system call descriptions for the Linux ppdev (parallel port) driver. Use when creating .txt and .txt.const files for fuzzing /dev/parportN devices, describing ppdev ioctls, resources, structs, flags, and computing ioctl command numbers.

Why use Syzkaller Ppdev Syzlang on TypingMind?

Because you install it once and use it with any model. Syzkaller Ppdev Syzlang is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Syzkaller Ppdev Syzlang in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Zhang-Henry/CoEvoSkills/tree/main/artifacts/skills/syzkaller-ppdev-syzlang/syzkaller-ppdev-syzlang. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Syzkaller Ppdev Syzlang?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Syzkaller Ppdev Syzlang?

As many as you like. As long as a model supports skills, you can use Syzkaller Ppdev Syzlang with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Syzkaller Ppdev Syzlang AI skill free?

Yes. It is published on GitHub by Zhang-Henry under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇