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

compression failed during “Create the input directory and the output directory for Janus” phase #8

Open
limbo-wg opened this issue Jun 25, 2021 · 3 comments

Comments

@limbo-wg
Copy link

when I run fuzzer after create seed programs, with the code:
./core/afl-image-syscall/afl-fuzz -b btrfs -s fs/btrfs/btrfs_wrapper.so -e ./samples/evaluation/btrfs-00.image -S btrfs -y prog -i input -o output -m none -u 2 -- ./lkl/tools/lkl/btrfs-combined -t btrfs -p @@

I got the outcome as follows:
afl-fuzz 2.52b by [email protected]
[+] [fs-fuzz] shm name to store image buffer: btrfs
[+] [fs-fuzz] target wrapper (.so) path: fs/btrfs/btrfs_wrapper.so
[+] [fs-fuzz] seed image path: ./samples/evaluation/btrfs-00.image
[+] [fs-fuzz] syscall input directory: prog
[+] You have 48 CPU cores and 1 runnable tasks (utilization: 2%).
[+] Try parallel jobs - see docs/parallel_fuzzing.txt.
[+] Found a free CPU core, binding to #2.
[] Checking core_pattern...
[
] Checking CPU scaling governor...
[+] [+] Open shm btrfs success.
[+] [+] Map shm btrfs at 0x7fdc3ac9b000 size: 0x8000000.

[-] image ./samples/evaluation/btrfs-00.image compression failed.
Location: compress(), btrfs_fuzzer.cc:211

can anyone tell me why I got this error?

@docfate111
Copy link

@limbo-wg I got the same email and also don't know why

@docfate111
Copy link

@r00tus3r
Copy link

I also came across this issue. I resolved it by increasing the shm size. (https://stackoverflow.com/questions/30210362/how-to-increase-the-size-of-the-dev-shm-in-docker-container)

By default it is 64 MB and the image file the program tries to read is 128 MB. So it is unable to read it fully.

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

3 participants