From: syzbot <syzbot+list25722e017155043d4db9@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
mhiramat@kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly trace report (Jan 2025)
Date: Mon, 13 Jan 2025 04:41:22 -0800 [thread overview]
Message-ID: <678509f2.050a0220.216c54.0054.GAE@google.com> (raw)
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 2 were fixed.
In total, 17 issues are still open and 41 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 2743 Yes possible deadlock in blk_trace_setup
https://syzkaller.appspot.com/bug?extid=0d8542c90a512dc95185
<2> 1434 Yes WARNING in format_decode (3)
https://syzkaller.appspot.com/bug?extid=e2c932aec5c8a6e1d31c
<3> 94 Yes WARNING in bpf_get_stack_raw_tp
https://syzkaller.appspot.com/bug?extid=ce35de20ed6652f60652
<4> 71 Yes WARNING: locking bug in __lock_task_sighand
https://syzkaller.appspot.com/bug?extid=97da3d7e0112d59971de
<5> 17 Yes WARNING in tracing_buffers_mmap_close
https://syzkaller.appspot.com/bug?extid=ddc001b92c083dbf2b97
<6> 15 Yes WARNING in get_probe_ref
https://syzkaller.appspot.com/bug?extid=8672dcb9d10011c0a160
<7> 5 Yes WARNING in tracepoint_probe_unregister (3)
https://syzkaller.appspot.com/bug?extid=a1d25e53cd4a10f7f2d3
---
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.
reply other threads:[~2025-01-13 12:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=678509f2.050a0220.216c54.0054.GAE@google.com \
--to=syzbot+list25722e017155043d4db9@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--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
all inboxes | Powered by JetHome®