On Thu, 23 Aug 2018 07:13:13 -0700 Dmitry Vyukov <dvyu...@google.com> wrote:
> On Thu, May 10, 2018 at 7:23 AM, Steven Rostedt <rost...@goodmis.org> wrote: > > On Thu, 10 May 2018 07:14:26 +0200 > > Dmitry Vyukov <dvyu...@google.com> wrote: > > > >> > IMPORTANT: if you fix the bug, please add the following tag to the > >> > commit: > >> > Reported-by: syzbot+5702a7e6d4a13b3ac...@syzkaller.appspotmail.com > >> > It will help syzbot understand when the bug is fixed. See footer for > >> > details. > >> > If you forward the report, please keep this part and the footer. > >> > >> > >> This was bisected to: > >> > >> commit 80765597bc587feae8dbc8ce97a0f32e12a6e625 > >> Author: Steven Rostedt (VMware) <rost...@goodmis.org> > >> Date: Fri Mar 9 13:19:28 2018 -0500 > >> > >> tracing: Rewrite filter logic to be simpler and faster > > > > I could have told you that without the bisect ;-) > > > > I'll try to get some time to look into this. > > > It seems this was lost on kernel mailing lists, then re-reported after 2 > months: > https://bugzilla.kernel.org/show_bug.cgi?id=200019 > and then fixed. Yeah, that time was quite busy for me. I guess I failed to get time to look into it when it was first reported :-( > > Since the fixing commit does not contain syzbot tag, need to tell it > about the fix manually: > > #syz fix: tracing: Check for no filter when processing event filters Sorry about that. Thanks, -- Steve
