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
There should probably be an easier way to integrate CFLite into projects integrated into OSS-Fuzz #61
Comments
In some sense ClusterFuzzLite is simply an interface into the same codebase as CIFuzz. |
On second thought there might be some issues with the above approach. |
If we can't go with something simple like the above approach, I probably won't do anything to support this. I think it would just add too much complexity to account for OSS-Fuzz projects that are in ClusterFuzzLite. |
Is there any advantage to adding ClusterFuzzLite to projects already on OSS-Fuzz? |
It's compatible with forks so I think it depends on whether it's important for projects to test their forks or not. systemd uses it to test stable branches (where releases consumed by some distributions are kept): systemd/systemd#22295 |
If that's the only reason, maybe we should just add fork support to CIFuzz. |
I think it would be great but I'm not sure how it can be implemented. For example CIFuzz always downloads the latest builds but CFLite shouldn't do that because the latest upstream builds don't match the latest "fork" builds. |
Ah makes sense. |
Regarding advantages I forgot to mention that CFLite is more configurable when it comes to forks in the sense that depending on what projects need they can either download public OSS-Fuzz corpora manually (systemd/systemd#22302) and let CFLite discover issues that haven't been caught when forks were created and backport relevant patches or rely on "stable" seed corpora to make sure forks are more or less fine in general. |
Even though I still think it would be great if there was an easier way it's already possible to do it and probably it doesn't make much sense to complicate things to cover those niche use cases. |
Trying to integrate CFLite into my fork of elfutils in evverx/elfutils#35, I basically just copied all the files from the elfutils directory to
$SRC/
I wonder if there is an easier way to do that?
The text was updated successfully, but these errors were encountered: