From: Dmitry Vyukov <dvyukov@google.com>
To: Oliver Neukum <oneukum@suse.com>
Cc: syzbot <syzbot+854768b99f19e89d7f81@syzkaller.appspotmail.com>,
bjorn@mork.no, USB list <linux-usb@vger.kernel.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
Andrey Konovalov <andreyknvl@google.com>
Subject: Re: INFO: task hung in wdm_flush
Date: Fri, 22 Nov 2019 10:11:03 +0100 [thread overview]
Message-ID: <CACT4Y+b1x-0yeY6HrZ3ZL4iP6hcNupD15uNNiFqx45LjDZgJ_w@mail.gmail.com> (raw)
In-Reply-To: <1574334450.14298.53.camel@suse.com>
On Thu, Nov 21, 2019 at 12:07 PM Oliver Neukum <oneukum@suse.com> wrote:
>
> Am Mittwoch, den 20.11.2019, 14:40 -0800 schrieb syzbot:
> > Hello,
> >
> > syzbot tried to test the proposed patch but build/boot failed:
> >
> > failed to apply patch:
> > checking file drivers/usb/class/cdc-wdm.c
> > Hunk #1 FAILED at 587.
> > Hunk #2 FAILED at 596.
> > 2 out of 2 hunks FAILED
>
> This is unexpected.
> >
> >
> >
> > Tested on:
> >
> > commit: e96407b4 usb-fuzzer: main usb gadget fuzzer driver
> > git tree: https://github.com/google/kasan.git
>
> If I do a git am on the branch usb-fuzzer-usb-testing-2019.11.19,
> the patch applies. Which branch do I need to backport to?
Hi Oliver,
You give exact tree/base commit when you ask syzbot to test. It does
not do any second guessing.
Well, if you provide a tree+branch then it's a bit of chasing a moving
target b/c HEAD can be updated meanwhile, but you can also give it
tree+commit, then that's 100% fixed.
next prev parent reply other threads:[~2019-11-22 9:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 13:21 INFO: task hung in wdm_flush Oliver Neukum
2019-11-20 22:40 ` syzbot
2019-11-21 11:07 ` Oliver Neukum
2019-11-22 9:11 ` Dmitry Vyukov [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-08-12 12:18 syzbot
2019-11-19 9:14 ` Bjørn Mork
2019-11-19 10:31 ` Oliver Neukum
2019-11-19 11:34 ` Bjørn Mork
2019-11-23 6:52 ` Dmitry Vyukov
2020-02-10 10:06 ` Dmitry Vyukov
2020-02-10 10:09 ` Dmitry Vyukov
2020-02-10 12:46 ` Tetsuo Handa
2020-02-10 15:04 ` Dmitry Vyukov
2020-02-10 15:06 ` Dmitry Vyukov
2020-02-10 15:21 ` Tetsuo Handa
2020-02-11 13:55 ` Tetsuo Handa
2020-02-11 14:11 ` Dmitry Vyukov
2020-02-11 14:01 ` 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+b1x-0yeY6HrZ3ZL4iP6hcNupD15uNNiFqx45LjDZgJ_w@mail.gmail.com \
--to=dvyukov@google.com \
--cc=andreyknvl@google.com \
--cc=bjorn@mork.no \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=syzbot+854768b99f19e89d7f81@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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;
as well as URLs for NNTP newsgroup(s).