* Issue 45637 in oss-fuzz: elfutils:fuzz-libelf: Timeout in fuzz-libelf
[not found] <0=71cc74a7ba1af446b7ed6b9a08b414d9=53ab637581f8c6bec81059b6169750a5=oss-fuzz@monorail-prod.appspotmail.com>
@ 2022-03-17 7:19 ` ClusterFuzz-External via monorail
2022-03-20 10:02 ` da… via monorail
` (2 subsequent siblings)
3 siblings, 0 replies; 4+ messages in thread
From: ClusterFuzz-External via monorail @ 2022-03-17 7:19 UTC (permalink / raw)
To: elfutils-devel
Status: New
Owner: ----
CC: elfut...@sourceware.org, da...@adalogics.com, evv...@gmail.com, izzeem@google.com
Labels: ClusterFuzz Reproducible Engine-libfuzzer OS-Linux Proj-elfutils Reported-2022-03-17
Type: Bug
New issue 45637 by ClusterFuzz-External: elfutils:fuzz-libelf: Timeout in fuzz-libelf
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45637
Detailed Report: https://oss-fuzz.com/testcase?key=6393240885002240
Project: elfutils
Fuzzing Engine: libFuzzer
Fuzz Target: fuzz-libelf
Job Type: libfuzzer_asan_elfutils
Platform Id: linux
Crash Type: Timeout (exceeds 60 secs)
Crash Address:
Crash State:
fuzz-libelf
Sanitizer: address (ASAN)
Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_elfutils&range=202203161800:202203170000
Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=6393240885002240
Issue filed automatically.
See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally.
When you fix this bug, please
* mention the fix revision(s).
* state whether the bug was a short-lived regression or an old bug in any stable releases.
* add any other useful information.
This information can help downstream consumers.
If you need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. Comments on individual Monorail issues are not monitored.
--
You received this message because:
1. You were specifically CC'd on the issue
You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings
Reply to this email to add a comment.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Issue 45637 in oss-fuzz: elfutils:fuzz-libelf: Timeout in fuzz-libelf
[not found] <0=71cc74a7ba1af446b7ed6b9a08b414d9=53ab637581f8c6bec81059b6169750a5=oss-fuzz@monorail-prod.appspotmail.com>
2022-03-17 7:19 ` Issue 45637 in oss-fuzz: elfutils:fuzz-libelf: Timeout in fuzz-libelf ClusterFuzz-External via monorail
@ 2022-03-20 10:02 ` da… via monorail
2022-03-20 10:03 ` da… via monorail
2022-03-22 15:08 ` ClusterFuzz-External via monorail
3 siblings, 0 replies; 4+ messages in thread
From: da… via monorail @ 2022-03-20 10:02 UTC (permalink / raw)
To: elfutils-devel
Comment #1 on issue 45637 by da...@adalogics.com: elfutils:fuzz-libelf: Timeout in fuzz-libelf
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45637#c1
ASAN report:
Running: /mnt/scratch0/clusterfuzz/bot/inputs/fuzzer-testcases/timeout-15f79e70f92567039dd67b7c3a16ad3a180b3a6e
ALARM: working on the last Unit for 61 seconds
and the timeout value is 60 (use -timeout=N to change)
==5980== ERROR: libFuzzer: timeout after 61 seconds
#0 0x52e5c1 in __sanitizer_print_stack_trace /src/llvm-project/compiler-rt/lib/asan/asan_stack.cpp:87:3
#1 0x46e9e8 in fuzzer::PrintStackTrace() /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerUtil.cpp:210:5
#2 0x453db9 in fuzzer::Fuzzer::AlarmCallback() /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:301:5
#3 0x7f7ca26eb3bf in libpthread.so.0
#4 0x571322 in elf_cvt_Verneed /src/elfutils/libelf/version_xlate.h:211:20
#5 0x56957e in convert_data /src/elfutils/libelf/elf_getdata.c:192:7
#6 0x56957e in __libelf_set_data_list_rdlock /src/elfutils/libelf/elf_getdata.c:453:7
#7 0x569a67 in __elf_getdata_rdlock /src/elfutils/libelf/elf_getdata.c:560:5
#8 0x569b1c in elf_getdata /src/elfutils/libelf/elf_getdata.c:578:12
#9 0x56d9d4 in elf_compress_gnu /src/elfutils/libelf/elf_compress_gnu.c:150:24
#10 0x55dbba in fuzz_logic_one /src/fuzz-libelf.c:48:15
#11 0x55e077 in LLVMFuzzerTestOneInput /src/fuzz-libelf.c:82:3
#12 0x4553f2 in fuzzer::Fuzzer::ExecuteCallback(unsigned char const*, unsigned long) /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:611:15
#13 0x440fa2 in fuzzer::RunOneTest(fuzzer::Fuzzer*, char const*, unsigned long) /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:324:6
#14 0x44680c in fuzzer::FuzzerDriver(int*, char***, int (*)(unsigned char const*, unsigned long)) /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:860:9
#15 0x46f1a2 in main /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerMain.cpp:20:10
#16 0x7f7ca24df0b2 in __libc_start_main /build/glibc-eX1tMB/glibc-2.31/csu/libc-start.c:308:16
#17 0x41f6ed in _start
--
You received this message because:
1. You were specifically CC'd on the issue
You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings
Reply to this email to add a comment.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Issue 45637 in oss-fuzz: elfutils:fuzz-libelf: Timeout in fuzz-libelf
[not found] <0=71cc74a7ba1af446b7ed6b9a08b414d9=53ab637581f8c6bec81059b6169750a5=oss-fuzz@monorail-prod.appspotmail.com>
2022-03-17 7:19 ` Issue 45637 in oss-fuzz: elfutils:fuzz-libelf: Timeout in fuzz-libelf ClusterFuzz-External via monorail
2022-03-20 10:02 ` da… via monorail
@ 2022-03-20 10:03 ` da… via monorail
2022-03-22 15:08 ` ClusterFuzz-External via monorail
3 siblings, 0 replies; 4+ messages in thread
From: da… via monorail @ 2022-03-20 10:03 UTC (permalink / raw)
To: elfutils-devel
Comment #2 on issue 45637 by da...@adalogics.com: elfutils:fuzz-libelf: Timeout in fuzz-libelf
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45637#c2
(No comment was entered for this change.)
Attachments:
clusterfuzz-testcase-minimized-fuzz-libelf-6393240885002240 684 bytes
--
You received this message because:
1. You were specifically CC'd on the issue
You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings
Reply to this email to add a comment.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Issue 45637 in oss-fuzz: elfutils:fuzz-libelf: Timeout in fuzz-libelf
[not found] <0=71cc74a7ba1af446b7ed6b9a08b414d9=53ab637581f8c6bec81059b6169750a5=oss-fuzz@monorail-prod.appspotmail.com>
` (2 preceding siblings ...)
2022-03-20 10:03 ` da… via monorail
@ 2022-03-22 15:08 ` ClusterFuzz-External via monorail
3 siblings, 0 replies; 4+ messages in thread
From: ClusterFuzz-External via monorail @ 2022-03-22 15:08 UTC (permalink / raw)
To: elfutils-devel
Updates:
Labels: ClusterFuzz-Verified
Status: Verified
Comment #3 on issue 45637 by ClusterFuzz-External: elfutils:fuzz-libelf: Timeout in fuzz-libelf
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45637#c3
ClusterFuzz testcase 6393240885002240 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_elfutils&range=202203210605:202203211200
If this is incorrect, please file a bug on https://github.com/google/oss-fuzz/issues/new
--
You received this message because:
1. You were specifically CC'd on the issue
You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings
Reply to this email to add a comment.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2022-03-22 15:08 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <0=71cc74a7ba1af446b7ed6b9a08b414d9=53ab637581f8c6bec81059b6169750a5=oss-fuzz@monorail-prod.appspotmail.com>
2022-03-17 7:19 ` Issue 45637 in oss-fuzz: elfutils:fuzz-libelf: Timeout in fuzz-libelf ClusterFuzz-External via monorail
2022-03-20 10:02 ` da… via monorail
2022-03-20 10:03 ` da… via monorail
2022-03-22 15:08 ` ClusterFuzz-External via monorail
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).