From: syzbot <syzbot+bb6d800770577a083f8c@syzkaller.appspotmail.com>
To: dvyukov@google.com, ktkhai@virtuozzo.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
miklos@szeredi.hu, mszeredi@redhat.com,
syzkaller-bugs@googlegroups.com
Subject: Re: INFO: task hung in fuse_reverse_inval_entry
Date: Thu, 07 Nov 2019 05:42:05 -0800 [thread overview]
Message-ID: <000000000000b8443c0596c1d480@google.com> (raw)
In-Reply-To: <000000000000bc17b60571a60434@google.com>
syzbot suspects this bug was fixed by commit:
commit c59fd85e4fd07fdf0ab523a5e9734f5338d6aa19
Author: Kirill Tkhai <ktkhai@virtuozzo.com>
Date: Tue Sep 11 10:11:56 2018 +0000
fuse: change interrupt requests allocation algorithm
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15518db2600000
start commit: d72e90f3 Linux 4.18-rc6
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=68af3495408deac5
dashboard link: https://syzkaller.appspot.com/bug?extid=bb6d800770577a083f8c
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11564d1c400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16fc570c400000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: fuse: change interrupt requests allocation algorithm
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2019-11-07 13:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-23 7:59 INFO: task hung in fuse_reverse_inval_entry syzbot
2018-07-23 8:11 ` Dmitry Vyukov
2018-07-23 12:12 ` Miklos Szeredi
2018-07-23 12:22 ` Dmitry Vyukov
2018-07-23 12:33 ` Miklos Szeredi
2018-07-23 12:46 ` Dmitry Vyukov
2018-07-23 13:05 ` Miklos Szeredi
2018-07-23 13:37 ` Dmitry Vyukov
2018-07-23 15:09 ` Miklos Szeredi
2018-07-23 15:19 ` Dmitry Vyukov
2018-07-24 15:17 ` Miklos Szeredi
2018-07-25 9:12 ` Dmitry Vyukov
2018-07-26 8:44 ` Miklos Szeredi
2018-07-26 9:12 ` Miklos Szeredi
2018-11-02 19:31 ` Dmitry Vyukov
2019-11-07 13:42 ` syzbot [this message]
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=000000000000b8443c0596c1d480@google.com \
--to=syzbot+bb6d800770577a083f8c@syzkaller.appspotmail.com \
--cc=dvyukov@google.com \
--cc=ktkhai@virtuozzo.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=mszeredi@redhat.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).