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

syzbot: exporting downloadable archives of the open/fixed bugs #5439

Open
a-nogikh opened this issue Oct 25, 2024 · 1 comment
Open

syzbot: exporting downloadable archives of the open/fixed bugs #5439

a-nogikh opened this issue Oct 25, 2024 · 1 comment

Comments

@a-nogikh
Copy link
Collaborator

a-nogikh commented Oct 25, 2024

We currently share bug lists and per-bug information via a JSON API which requires multiple queries (linear to the number of bugs) and which is subject to request throttling.

There have been a number of requests from external and internal parties that could be resolved by sharing a downloadable .tar.gz archive with all that information.

So far, it looks like the archive should be of the following form:

  1. Multiple folders at root, one folder per bug.
  2. For each bug, a JSON description with the basic information (title, status, fix/cause bisections).
  3. For each bug, a crashes folder with N (up to 10?) most relevant crashes. For each crash:
    3.a) General info (crash title, date, arch, kernel and syzkaller revisions)
    3.b) Crash report
    3.c) C and Syz reproducers (if present).

There are two ways we could implement it:

  1. Construct and upload the archive directly from GAE.
  2. Invoke a standalone tool (like tools/syz-reprolist) that will make all those API queries to the Web dashboard (without throttling) and construct the archive.

Cc @tarasmadan

@tarasmadan
Copy link
Collaborator

#5468 to store bugs+crashes

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

No branches or pull requests

2 participants