From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: syzbot <syzbot+list0820d438c1905c75bc71@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, bpf@vger.kernel.org
Subject: Re: [syzbot] Monthly trace report (May 2024)
Date: Sun, 2 Jun 2024 12:09:50 +0900 [thread overview]
Message-ID: <20240602120950.8f08ef16ad9c485db374c08d@kernel.org> (raw)
In-Reply-To: <00000000000061fac40619ba66f6@google.com>
On Thu, 30 May 2024 23:50:32 -0700
syzbot <syzbot+list0820d438c1905c75bc71@syzkaller.appspotmail.com> wrote:
> Hello trace maintainers/developers,
>
> This is a 31-day syzbot report for the trace subsystem.
> All related reports/information can be found at:
> https://syzkaller.appspot.com/upstream/s/trace
>
> During the period, 1 new issues were detected and 0 were fixed.
> In total, 10 issues are still open and 35 have been fixed so far.
>
> Some of the still happening issues:
>
> Ref Crashes Repro Title
> <1> 705 Yes WARNING in format_decode (3)
> https://syzkaller.appspot.com/bug?extid=e2c932aec5c8a6e1d31c
Could you send this to bpf folks? It seems bpf_trace_printk caused this errror.
(Maybe skipping fmt string check?)
> <2> 26 Yes INFO: task hung in blk_trace_ioctl (4)
> https://syzkaller.appspot.com/bug?extid=ed812ed461471ab17a0c
This looks like debugfs_mutex lock leakage. Need to rerun with lockdep.
> <3> 7 Yes WARNING in get_probe_ref
> https://syzkaller.appspot.com/bug?extid=8672dcb9d10011c0a160
Hm, fail on register_trace_block_rq_insert(). blktrace issue.
> <4> 6 Yes INFO: task hung in blk_trace_remove (2)
> https://syzkaller.appspot.com/bug?extid=2373f6be3e6de4f92562
This looks like debugfs_mutex lock leakage too.
> <5> 5 Yes general protection fault in bpf_get_attach_cookie_tracing
> https://syzkaller.appspot.com/bug?extid=3ab78ff125b7979e45f9
This is also BPF problem.
Thank you,
>
> ---
> This report is generated by a bot. It may contain errors.
> See https://goo.gl/tpsmEJ for more information about syzbot.
> syzbot engineers can be reached at syzkaller@googlegroups.com.
>
> To disable reminders for individual bugs, reply with the following command:
> #syz set <Ref> no-reminders
>
> To change bug's subsystems, reply with:
> #syz set <Ref> subsystems: new-subsystem
>
> You may send multiple commands in a single email message.
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2024-06-02 3:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 6:50 [syzbot] Monthly trace report (May 2024) syzbot
2024-06-02 3:09 ` Masami Hiramatsu [this message]
2024-06-02 20:52 ` Jiri Olsa
2024-06-02 21:06 ` Jiri Olsa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240602120950.8f08ef16ad9c485db374c08d@kernel.org \
--to=mhiramat@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=syzbot+list0820d438c1905c75bc71@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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 NNTP newsgroup(s).