linux-kernel - Re: KASAN: slab-out-of-bounds Write in process

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CACT4Y+agmMRmey6XeMV3tJ1riNNdcO6Wqt2QZ4CEKs3nZHEp_g@mail.gmail.com>
Date:   Fri, 24 Aug 2018 10:46:23 -0700
From:   Dmitry Vyukov <dvyukov@...gle.com>
To:     Steven Rostedt <rostedt@...dmis.org>
Cc:     syzbot <syzbot+5702a7e6d4a13b3accd5@...kaller.appspotmail.com>,
        LKML <linux-kernel@...r.kernel.org>,
        Ingo Molnar <mingo@...hat.com>,
        syzkaller-bugs <syzkaller-bugs@...glegroups.com>,
        Al Viro <viro@...iv.linux.org.uk>
Subject: Re: KASAN: slab-out-of-bounds Write in process_preds

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

Hi Steven,

No personal criticism meant. I guess this is an inevitable consequence
of the current kernel development process and tooling. Reports and
patches get lots on a regular basis. In some subsystems we don't hear
from maintainers at all. That's one of the things we wanted to solve
with the syzbot dashboard: no thing get lost ever:
https://syzkaller.appspot.com/#upstream
But the other side of the medal is that bug report statues need to be
maintained.