From: Dmitry Vyukov <dvyukov@google.com>
To: Vladis Dronov <vdronov@redhat.com>
Cc: syzbot
<bot+c99ecc8a2c68eb7e06cf2f652e60d63d6fbe2f31@syzkaller.appspotmail.com>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Johan Hovold <johan@kernel.org>,
kai.heng.feng@canonical.com, LKML <linux-kernel@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>
Subject: Re: general protection fault in usb_find_alt_setting
Date: Sun, 23 Sep 2018 18:27:24 +0200 [thread overview]
Message-ID: <CACT4Y+anBfjFnKget7zu75uZVOV6ZT3-RPshaVt2a_4R3ararg@mail.gmail.com> (raw)
In-Reply-To: <1722725855.15417291.1537693865632.JavaMail.zimbra@redhat.com>
On Sun, Sep 23, 2018 at 11:11 AM, Vladis Dronov <vdronov@redhat.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.
next parent reply other threads:[~2018-09-23 16:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <956405482.15417289.1537693839327.JavaMail.zimbra@redhat.com>
[not found] ` <1722725855.15417291.1537693865632.JavaMail.zimbra@redhat.com>
2018-09-23 16:27 ` Dmitry Vyukov [this message]
2018-09-23 21:15 ` Vladis Dronov
2018-09-24 13:15 ` Dmitry Vyukov
[not found] <94eb2c05b4ba7e98d2055dc57696@google.com>
2018-05-11 17:39 ` 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=CACT4Y+anBfjFnKget7zu75uZVOV6ZT3-RPshaVt2a_4R3ararg@mail.gmail.com \
--to=dvyukov@google.com \
--cc=bot+c99ecc8a2c68eb7e06cf2f652e60d63d6fbe2f31@syzkaller.appspotmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=kai.heng.feng@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vdronov@redhat.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
all inboxes | Powered by JetHome®