Coverage report not generated
186 views
Skip to first unread message
Kainaat Singh
Feb 5, 2021, 2:31:43 PM2/5/21
to syzkaller
Hello,
The command to generate a coverage report in the following document does not generate anything. The csv report gets generated:
My command: ./bin/syz-cover --kernel_obj /home/kainaat/linux/ rawcover
Using verbose, it does not print anything.
Also, will the generated coverage report also include the highlighted source code as seen on the web interface?
Kainaat Singh
Feb 5, 2021, 5:40:54 PM2/5/21
to Jouni Högander, syzk...@googlegroups.com
Hello,
Thanks I found it.
I seem to be getting a known issue in Syzkaller:
"open drivers/gpu/drm/i915/i915_active.c: no such file or directory"
It is able to pick up header files but not the C source files. I don't want to update the kernel source. Is there another way around this?
On Fri, Feb 5, 2021 at 9:07 PM Jouni Högander <jouni.h...@unikie.com> wrote:
Hello,I think it is supposed to create html report into /tmp directory and open it in your browser. Is that /tmp/syz-cover* generated?BR,Jouni Högander
--
You received this message because you are subscribed to the Google Groups "syzkaller" group.
To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller/c76fcecd-e334-4da8-bf37-a414b1fb81b9n%40googlegroups.com.
Dmitry Vyukov
Feb 9, 2021, 2:39:35 AM2/9/21
to Kainaat Singh, Jouni Högander, syzkaller
On Fri, Feb 5, 2021 at 11:40 PM Kainaat Singh <savvy....@gmail.com> wrote:
>
> Hello,
>
> Thanks I found it.
>
> I seem to be getting a known issue in Syzkaller:
> "open drivers/gpu/drm/i915/i915_active.c: no such file or directory"
>
> It is able to pick up header files but not the C source files. I don't want to update the kernel source. Is there another way around this?
Hi Kainaat,
>
> Hello,
>
> Thanks I found it.
>
> I seem to be getting a known issue in Syzkaller:
> "open drivers/gpu/drm/i915/i915_active.c: no such file or directory"
>
> It is able to pick up header files but not the C source files. I don't want to update the kernel source. Is there another way around this?
It is not possible to generate a coverage report without having access
to source files because coverage report includes source files as the
main part.
I think currently pkg/report does not fail if a single source file is
missing. Perhaps you just need to update to HEAD.
> On Fri, Feb 5, 2021 at 9:07 PM Jouni Högander <jouni.h...@unikie.com> wrote:
>>
>> Hello,
>>
>> I think it is supposed to create html report into /tmp directory and open it in your browser. Is that /tmp/syz-cover* generated?
>>
>> BR,
>>
>> Jouni Högander
>>
>>
>>
>> pe 5. helmik. 2021 klo 21.31 Kainaat Singh <savvy....@gmail.com> kirjoitti:
>>>
>>> Hello,
>>>
>>> The command to generate a coverage report in the following document does not generate anything. The csv report gets generated:
>>> coverage.md
>>>
>>> My command: ./bin/syz-cover --kernel_obj /home/kainaat/linux/ rawcover
>>>
>>> Using verbose, it does not print anything.
>>>
>>> Also, will the generated coverage report also include the highlighted source code as seen on the web interface?
>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups "syzkaller" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller+...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller/c76fcecd-e334-4da8-bf37-a414b1fb81b9n%40googlegroups.com.
>
> --
> You received this message because you are subscribed to the Google Groups "syzkaller" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller+...@googlegroups.com.
Kainaat Singh
Feb 11, 2021, 1:36:24 PM2/11/21
to syzkaller
Hello Dmitry,
There is access to all the source code files. pkg/report seems to be failing on all the C source code files. On all of them I get the error: "open <filepath>: no such file or directory".
But, I am able to view all the header files in the generated report.
I updated the head and still I get the same error on all the C source code files. Do I need to rebuild the kernel after the update for the coverage report to work?
Kainaat Singh
Feb 11, 2021, 1:42:35 PM2/11/21
to syzkaller
Hello Dmitry,
Just wanted to inform you that I am trying to generate the coverage report from the downloaded rawcover using syz-cover.
Dmitry Vyukov
Feb 12, 2021, 4:52:54 AM2/12/21
to Kainaat Singh, syzkaller
On Thu, Feb 11, 2021 at 7:36 PM Kainaat Singh <savvy....@gmail.com> wrote:
>
> Hello Dmitry,
>
> There is access to all the source code files. pkg/report seems to be failing on all the C source code files. On all of them I get the error: "open <filepath>: no such file or directory".
>
> But, I am able to view all the header files in the generated report.
>
> I updated the head and still I get the same error on all the C source code files. Do I need to rebuild the kernel after the update for the coverage report to work?
No, you don't need to rebuild kernel.
>
> Hello Dmitry,
>
> There is access to all the source code files. pkg/report seems to be failing on all the C source code files. On all of them I get the error: "open <filepath>: no such file or directory".
>
> But, I am able to view all the header files in the generated report.
>
> I updated the head and still I get the same error on all the C source code files. Do I need to rebuild the kernel after the update for the coverage report to work?
You probably specified -kernel_src, -kernel_obj flags incorrectly.
The "drivers/gpu/drm/i915/i915_active.c" path is literally what it
tried to open from the current dir. Double check that you have this
path in the dir where you run syz-cover.
Reply all
Reply to author
Forward
0 new messages