From: Steven Rostedt <rostedt@goodmis.org>
To: Aleksandr Nogikh <nogikh@google.com>
Cc: syzbot
<syzbot+list3bf21e6ac0139f8d008d@syzkaller.appspotmail.com>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
mhiramat@kernel.org, syzkaller-bugs@googlegroups.com,
Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [syzbot] Monthly trace report (Oct 2024)
Date: Tue, 15 Oct 2024 10:05:12 -0400 [thread overview]
Message-ID: <20241015100512.54e5e840@gandalf.local.home> (raw)
In-Reply-To: <CANp29Y4KERQxwOwMCW5a4+YahhA8gWyJ=btE=OxnNgrF6puFgw@mail.gmail.com>
On Tue, 15 Oct 2024 12:05:29 +0200
Aleksandr Nogikh <nogikh@google.com> wrote:
> > None of these look like they are tracing infrastructure related.
>
> Like get_maintainer.pl, syzbot relies on the MAINTAINERS file to
> attribute bugs to the individual kernel subsystems. If several ones
> are suitable, the bug is assigned several labels at once. It's now
> actually the case for all open "trace" findings:
>
> https://syzkaller.appspot.com/upstream/s/trace
>
> (FWIW it's also possible to manually overwrite these labels and remove
> specific bugs from the monthly reports).
>
> I could make syzbot set "trace" only if there's no other good
> candidate, but I wonder if that could hide the findings in the trace
> infrastructure that manifested themselves in some specific traced
> subsystem.
>
I don't mind being Cc'd to these bugs. What I do mind is that only the
tracing maintainers are Cc'd. I still care about these, because they do
depend on the tracing code, and it could be the tracing infrastructure's
fault. But if an error is in a file that is explicitly called out in the
maintainers file, such as, blktrace.c and bpf_trace.c, then PLEASE also Cc
the maintainers of those files!
I had to manually add those maintainers when I replied to the initial
email. That is something I shouldn't need to do.
-- Steve
prev parent reply other threads:[~2024-10-15 14:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 15:25 [syzbot] Monthly trace report (Oct 2024) syzbot
2024-10-11 16:00 ` Steven Rostedt
2024-10-11 19:16 ` Jens Axboe
2024-10-15 10:05 ` Aleksandr Nogikh
2024-10-15 14:05 ` Steven Rostedt [this message]
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=20241015100512.54e5e840@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=axboe@kernel.dk \
--cc=bpf@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=nogikh@google.com \
--cc=syzbot+list3bf21e6ac0139f8d008d@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