public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot <syzbot+5702a7e6d4a13b3accd5@syzkaller.appspotmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@redhat.com>,
	syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
	Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: KASAN: slab-out-of-bounds Write in process_preds
Date: Thu, 23 Aug 2018 21:03:15 -0400	[thread overview]
Message-ID: <20180823210315.2449cf3e@vmware.local.home> (raw)
In-Reply-To: <CACT4Y+bSBgbSntkdEXFD+_aJZOrtMfm_WB0K7-psYVSVCg8vTg@mail.gmail.com>

On Thu, 23 Aug 2018 07:13:13 -0700
Dmitry Vyukov <dvyukov@google.com> wrote:

> On Thu, May 10, 2018 at 7:23 AM, Steven Rostedt <rostedt@goodmis.org> wrote:
> > On Thu, 10 May 2018 07:14:26 +0200
> > Dmitry Vyukov <dvyukov@google.com> wrote:
> >  
> >> > IMPORTANT: if you fix the bug, please add the following tag to the commit:
> >> > Reported-by: syzbot+5702a7e6d4a13b3accd5@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) <rostedt@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

  reply	other threads:[~2018-08-24  1:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-11 12:02 KASAN: slab-out-of-bounds Write in process_preds syzbot
2018-05-10  5:14 ` Dmitry Vyukov
2018-05-10 14:23   ` Steven Rostedt
2018-05-11 13:52     ` Dmitry Vyukov
2018-08-23 14:13     ` Dmitry Vyukov
2018-08-24  1:03       ` Steven Rostedt [this message]
2018-08-24 17:46         ` Dmitry Vyukov

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=20180823210315.2449cf3e@vmware.local.home \
    --to=rostedt@goodmis.org \
    --cc=dvyukov@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=syzbot+5702a7e6d4a13b3accd5@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=viro@zeniv.linux.org.uk \
    /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