Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

syzlang: recognizable file extensions #2524

Open
xairy opened this issue Mar 28, 2021 · 3 comments
Open

syzlang: recognizable file extensions #2524

xairy opened this issue Mar 28, 2021 · 3 comments

Comments

@xairy
Copy link
Collaborator

xairy commented Mar 28, 2021

Currently, syzkaller uses the .txt file extension for syzlang descriptions and uses no file extension for syzlang programs. It would be great to define, document, and use recognizable file extensions for both. This can be useful for e.g. text editors to recognize file format and enable proper syntax highlighting.

Options that come to mind:

  • .syz for descriptions and .prog for programs;
  • .syzlang for descriptions and .syzprog for programs
@xairy
Copy link
Collaborator Author

xairy commented Apr 30, 2021

Standardizing file extensions will also potentially allow adding syntax highlighting on Github.

@dvyukov
Copy link
Collaborator

dvyukov commented May 3, 2021

I don't mind adding recognizable extensions, but also don't consider it as important enough to work on this myself right now ;)

.prog looks too generic and not syzkaller-specific. I think programs should be .syz because they are more widely distributed with bug reports and used by wider audience, so it makes sense to have shorter/nicer extension for them.

Descriptions are only located in syzkaller sources and used by syzkaller contributors. .syzlang feels a bit long on my taste, but I can't think of anything better... probably it's a fine description.

@xairy
Copy link
Collaborator Author

xairy commented May 3, 2021

Another idea: szp for programs and szl for syzlang. Both are short and unique. However, less recognizable.

I also don't have plans to work in this, at least in the foreseeable future. Maybe someone will step in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants