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

report: generate links to source in reports #5

Closed
dvyukov opened this issue Nov 24, 2015 · 1 comment
Closed

report: generate links to source in reports #5

dvyukov opened this issue Nov 24, 2015 · 1 comment

Comments

@dvyukov
Copy link
Collaborator

dvyukov commented Nov 24, 2015

git.kernel.org provides a way to show a particular source line on particular commit:

https://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/tree/net/sctp/sm_sideeffect.c?id=4dd191bb6195641edbc527a8495b7b1b816a41e6#n1097

We could embed such links into reports. Probably work for kasan_symbolize.py script.

@dvyukov dvyukov changed the title Generate links to source in reports report: generate links to source in reports May 26, 2017
@dvyukov
Copy link
Collaborator Author

dvyukov commented Aug 12, 2017

Obsolete

@dvyukov dvyukov closed this as completed Aug 12, 2017
dvyukov added a commit to dvyukov/syzkaller that referenced this issue Mar 13, 2020
ThreadSanitizer says:

WARNING: ThreadSanitizer: data race (pid=3)
  Atomic read of size 4 at 0x56360e562f08 by main thread:
    #0 __tsan_atomic32_load <null> (libtsan.so.0+0x64249)
    #1 event_isset executor/common_linux.h:51 (syz-executor.0+0x2cf1f)
    #2 handle_completion executor/executor.cc:886 (syz-executor.0+0x2cf1f)
    #3 execute_one executor/executor.cc:732 (syz-executor.0+0x2da3b)
    #4 loop executor/common.h:581 (syz-executor.0+0x2f1aa)
    google#5 do_sandbox_none executor/common_linux.h:2694 (syz-executor.0+0x189d6)
    google#6 main executor/executor.cc:407 (syz-executor.0+0x189d6)

  Previous write of size 4 at 0x56360e562f08 by thread T1:
    #0 event_reset executor/common_linux.h:32 (syz-executor.0+0x1f5af)
    #1 worker_thread executor/executor.cc:1048 (syz-executor.0+0x1f5af)
    #2 <null> <null> (libtsan.so.0+0x2b0b6)

  Location is global 'threads' of size 2560 at 0x56360e562f00 (syz-executor.0+0x00000008bf08)

  Thread T1 (tid=6, running) created by main thread at:
    #0 pthread_create <null> (libtsan.so.0+0x2d55b)
    #1 thread_start executor/common.h:256 (syz-executor.0+0x2d707)
    #2 thread_create executor/executor.cc:1037 (syz-executor.0+0x2d707)
    #3 schedule_call executor/executor.cc:811 (syz-executor.0+0x2d707)
    #4 execute_one executor/executor.cc:719 (syz-executor.0+0x2d707)
    google#5 loop executor/common.h:581 (syz-executor.0+0x2f1aa)
    google#6 do_sandbox_none executor/common_linux.h:2694 (syz-executor.0+0x189d6)
    google#7 main executor/executor.cc:407 (syz-executor.0+0x189d6)
dvyukov added a commit that referenced this issue Mar 13, 2020
ThreadSanitizer says:

WARNING: ThreadSanitizer: data race (pid=3)
  Atomic read of size 4 at 0x56360e562f08 by main thread:
    #0 __tsan_atomic32_load <null> (libtsan.so.0+0x64249)
    #1 event_isset executor/common_linux.h:51 (syz-executor.0+0x2cf1f)
    #2 handle_completion executor/executor.cc:886 (syz-executor.0+0x2cf1f)
    #3 execute_one executor/executor.cc:732 (syz-executor.0+0x2da3b)
    #4 loop executor/common.h:581 (syz-executor.0+0x2f1aa)
    #5 do_sandbox_none executor/common_linux.h:2694 (syz-executor.0+0x189d6)
    #6 main executor/executor.cc:407 (syz-executor.0+0x189d6)

  Previous write of size 4 at 0x56360e562f08 by thread T1:
    #0 event_reset executor/common_linux.h:32 (syz-executor.0+0x1f5af)
    #1 worker_thread executor/executor.cc:1048 (syz-executor.0+0x1f5af)
    #2 <null> <null> (libtsan.so.0+0x2b0b6)

  Location is global 'threads' of size 2560 at 0x56360e562f00 (syz-executor.0+0x00000008bf08)

  Thread T1 (tid=6, running) created by main thread at:
    #0 pthread_create <null> (libtsan.so.0+0x2d55b)
    #1 thread_start executor/common.h:256 (syz-executor.0+0x2d707)
    #2 thread_create executor/executor.cc:1037 (syz-executor.0+0x2d707)
    #3 schedule_call executor/executor.cc:811 (syz-executor.0+0x2d707)
    #4 execute_one executor/executor.cc:719 (syz-executor.0+0x2d707)
    #5 loop executor/common.h:581 (syz-executor.0+0x2f1aa)
    #6 do_sandbox_none executor/common_linux.h:2694 (syz-executor.0+0x189d6)
    #7 main executor/executor.cc:407 (syz-executor.0+0x189d6)
dvyukov added a commit that referenced this issue Jul 16, 2020
It seems that different gcc's have different defaults for ASAN flags.
Some fail with:

        run.go:67: nonfailing none/thr/repeat            : FAIL: run 0: call 0 is not executed
            	ASAN:DEADLYSIGNAL
            	=================================================================
            	==67143==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x7f7b0befb0a2 bp 0x7f7b0cfdad10 sp 0x7f7b0cfda490 T1)
            	    #0 0x7f7b0befb0a1  (/usr/lib/x86_64-linux-gnu/libasan.so.3+0x8d0a1)
            	    #1 0x404bbb in syz_compare(long, long, long, long) (/tmp/utor355225125.0+0x404bbb)
            	    #2 0x403cdf in execute_call(thread_t*) (/tmp/utor355225125.0+0x403cdf)
            	    #3 0x404006 in worker_thread(void*) (/tmp/utor355225125.0+0x404006)
            	    #4 0x7f7b0bc584a3 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x74a3)
            	    #5 0x7f7b0b99ad0e in __clone (/lib/x86_64-linux-gnu/libc.so.6+0xe8d0e)

            	AddressSanitizer can not provide additional info.
            	SUMMARY: AddressSanitizer: SEGV (/usr/lib/x86_64-linux-gnu/libasan.so.3+0x8d0a1)
            	Thread T1 created by T0 here:
            	    #0 0x7f7b0be9ef59 in __interceptor_pthread_create (/usr/lib/x86_64-linux-gnu/libasan.so.3+0x30f59)
            	    #1 0x406117 in execute_one() (/tmp/utor355225125.0+0x406117)
tnarg999 pushed a commit to tnarg999/syzkaller that referenced this issue Aug 10, 2021
@gkennedy12 gkennedy12 mentioned this issue Jul 19, 2022
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

1 participant