From: syzbot <syzbot+9468df99cb63a4a4c4e1@syzkaller.appspotmail.com>
To: andreyknvl@google.com, brookebasile@gmail.com,
chunkeey@googlemail.com, davem@davemloft.net,
gregkh@linuxfoundation.org, ingrassia@epigenesys.com,
jack@suse.cz, kuba@kernel.org, kvalo@codeaurora.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com, tytso@mit.edu,
yi.zhang@huawei.com
Subject: Re: WARNING in carl9170_usb_submit_cmd_urb/usb_submit_urb
Date: Thu, 04 Mar 2021 06:29:06 -0800 [thread overview]
Message-ID: <0000000000003d692a05bcb6ca26@google.com> (raw)
In-Reply-To: <0000000000004dbaa505a5a165f7@google.com>
syzbot has bisected this issue to:
commit 6a66a7ded12baa6ebbb2e3e82f8cb91382814839
Author: zhangyi (F) <yi.zhang@huawei.com>
Date: Thu Feb 13 06:38:20 2020 +0000
jbd2: move the clearing of b_modified flag to the journal_unmap_buffer()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14bd498ed00000
start commit: f69d02e3 Merge tag 'misc-5.12-2021-03-02' of git://git.ker..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=16bd498ed00000
console output: https://syzkaller.appspot.com/x/log.txt?x=12bd498ed00000
kernel config: https://syzkaller.appspot.com/x/.config?x=e0da2d01cc636e2c
dashboard link: https://syzkaller.appspot.com/bug?extid=9468df99cb63a4a4c4e1
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11770346d00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17be69ccd00000
Reported-by: syzbot+9468df99cb63a4a4c4e1@syzkaller.appspotmail.com
Fixes: 6a66a7ded12b ("jbd2: move the clearing of b_modified flag to the journal_unmap_buffer()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
parent reply other threads:[~2021-03-04 14:30 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <0000000000004dbaa505a5a165f7@google.com>]
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=0000000000003d692a05bcb6ca26@google.com \
--to=syzbot+9468df99cb63a4a4c4e1@syzkaller.appspotmail.com \
--cc=andreyknvl@google.com \
--cc=brookebasile@gmail.com \
--cc=chunkeey@googlemail.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=ingrassia@epigenesys.com \
--cc=jack@suse.cz \
--cc=kuba@kernel.org \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
--cc=yi.zhang@huawei.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).