From: Steven Rostedt <rostedt@goodmis.org>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot <syzbot+704bfe2c7d156640ad7a@syzkaller.appspotmail.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
arvid.brodin@alten.se, Alexei Starovoitov <ast@kernel.org>,
bpf <bpf@vger.kernel.org>, Daniel Borkmann <daniel@iogearbox.net>,
David Miller <davem@davemloft.net>, Josef Bacik <jbacik@fb.com>,
jolsa@redhat.com, Martin KaFai Lau <kafai@fb.com>,
kernel-team@fb.com, LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
netdev <netdev@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Song Liu <songliubraving@fb.com>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Cong Wang <xiyou.wangcong@gmail.com>, Yonghong Song <yhs@fb.com>
Subject: Re: WARNING in add_event_to_ctx
Date: Fri, 10 Jan 2020 10:01:49 -0500 [thread overview]
Message-ID: <20200110100149.58ef4893@gandalf.local.home> (raw)
In-Reply-To: <CACT4Y+Z2M3p+26KROAAnGH-HuuWZdu8Cx1TrN7YhWTh9Exj+rQ@mail.gmail.com>
On Fri, 10 Jan 2020 15:48:34 +0100
Dmitry Vyukov <dvyukov@google.com> wrote:
> On Fri, Jan 10, 2020 at 3:45 PM Steven Rostedt <rostedt@goodmis.org> wrote:
> >
> > On Thu, 09 Jan 2020 22:50:00 -0800
> > syzbot <syzbot+704bfe2c7d156640ad7a@syzkaller.appspotmail.com> wrote:
> >
> > > syzbot suspects this bug was fixed by commit:
> >
> > I think these reports need some more information. Like the sample crash
> > report, so we don't need to be clicking through links to find it.
> > Because I have no idea what bug was fixed.
>
> Hi Steve,
>
> Isn't it threaded to the original report in your client? The message
> has both matching subject and In-Reply-To header. At least that was
> the idea.
>
Ah, if I go to lore.kernel.org, I see the original report. But that's
from back in June. I only keep up to two months of emails before I
archive them.
Perhaps add something like:
Original report: https://lore.kernel.org/bpf/000000000000946842058bc1291d@google.com/
?
Thanks!
-- Steve
prev parent reply other threads:[~2020-01-10 15:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 13:17 WARNING in add_event_to_ctx syzbot
2019-06-20 14:39 ` syzbot
2020-01-10 6:50 ` syzbot
2020-01-10 14:45 ` Steven Rostedt
2020-01-10 14:48 ` Dmitry Vyukov
2020-01-10 15:01 ` 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=20200110100149.58ef4893@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=arvid.brodin@alten.se \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=jbacik@fb.com \
--cc=jolsa@redhat.com \
--cc=kafai@fb.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=songliubraving@fb.com \
--cc=syzbot+704bfe2c7d156640ad7a@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=xiyou.wangcong@gmail.com \
--cc=yhs@fb.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).