Skip to content

Remove modules irrelevant to afl-qemu-trace #64

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

McSinyx
Copy link

@McSinyx McSinyx commented May 19, 2025

  • dtc, roms/* and slirp are for system emulation
  • capstone is not utilized in fuzzing scenarios with AFL++
  • meson >= 0.55.3 is available on all supported distro releases

This helps majorly with fetching time for packaging downstream.

@McSinyx McSinyx force-pushed the afl++-sans-system-modules branch from c0235f8 to 9ca69f4 Compare May 19, 2025 10:03
* dtc, roms/* and slirp are for system emulation
* capstone is not utilized in fuzzing scenarios with AFL++
* meson >= 0.55.3 is available on all supported distro releases
@McSinyx McSinyx force-pushed the afl++-sans-system-modules branch from 9ca69f4 to 07eb1a9 Compare May 22, 2025 06:39
@McSinyx McSinyx changed the title Remove modules relevant to afl-qemu-trace Remove modules irrelevant to afl-qemu-trace May 22, 2025
@vanhauser-thc
Copy link
Member

Also I understand the intent this also creates problems. e.g. removing capstone removes the ability to debug assembly if weird problems happen

@McSinyx
Copy link
Author

McSinyx commented Jun 30, 2025

How about the other submodules? I don't think AFL++ works with system emulation and the required meson version is no longer exotic.

Capstone repository is not that heavy so bundling it in the source tree is reasonable, fetch-performance-wise, even though QEMU doesn't really modify it and most distributions do include and link it with vanilla QEMU. BTW is Capstone integration still works with QEMU for AFL++?

@vanhauser-thc
Copy link
Member

I agree that a lot of those modules can be removed. some are obvious whereas for others I would be clueless if they are needed or not without investing time I do not have.
As I do not know you I cannot totally rely on your judgement alone here :)

if you can redo the the PR to remove only those that are obviously not needed for user-mode qemu then I will happily merge it.

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

Successfully merging this pull request may close these issues.

2 participants