[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACT4Y+anBfjFnKget7zu75uZVOV6ZT3-RPshaVt2a_4R3ararg@mail.gmail.com>
Date: Sun, 23 Sep 2018 18:27:24 +0200
From: Dmitry Vyukov <dvyukov@...gle.com>
To: Vladis Dronov <vdronov@...hat.com>
Cc: syzbot
<bot+c99ecc8a2c68eb7e06cf2f652e60d63d6fbe2f31@...kaller.appspotmail.com>,
syzkaller-bugs <syzkaller-bugs@...glegroups.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Johan Hovold <johan@...nel.org>, kai.heng.feng@...onical.com,
LKML <linux-kernel@...r.kernel.org>,
USB list <linux-usb@...r.kernel.org>
Subject: Re: general protection fault in usb_find_alt_setting
On Sun, Sep 23, 2018 at 11:11 AM, Vladis Dronov <vdronov@...hat.com> wrote:
> #syz fix: USB: handle NULL config in usb_find_alt_setting()
> #syz dup: general protection fault in usb_find_alt_setting (2)
Same here.
syzbot process designed in such way that it will not open second
version of the bug (2) for the same bug. syzbot waits until the fixing
commit reaches all tested tree and only then closes a bug. If the
crash is spotted again _after_ that, then syzbot creates second
version of the bug (2). But at that point it has to be a different bug
requiring a different fix.
So this should not be a dup, and should not fixed with the same commit
as the first version.
Powered by blists - more mailing lists