From: syzbot <syzbot+44c32606d8669fb0d45c@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, axboe@kernel.dk, dave@stgolabs.net,
hch@lst.de, linux-block@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, ming.lei@redhat.com, osandov@fb.com,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: INFO: task hung in __generic_file_fsync (2)
Date: Sat, 01 Feb 2020 23:05:01 -0800 [thread overview]
Message-ID: <000000000000e76ba6059d926c08@google.com> (raw)
In-Reply-To: <0000000000001a1ef1059b1a27c7@google.com>
syzbot suspects this bug was fixed by commit:
commit 85a8ce62c2eabe28b9d76ca4eecf37922402df93
Author: Ming Lei <ming.lei@redhat.com>
Date: Fri Dec 27 23:05:48 2019 +0000
block: add bio_truncate to fix guard_bio_eod
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13ebe101e00000
start commit: bf8d1cd4 Merge tag 'scsi-fixes' of git://git.kernel.org/pu..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=ed9d672709340e35
dashboard link: https://syzkaller.appspot.com/bug?extid=44c32606d8669fb0d45c
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=137e2615e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11306971e00000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: block: add bio_truncate to fix guard_bio_eod
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2020-02-02 7:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-01 20:45 INFO: task hung in __generic_file_fsync (2) syzbot
2020-01-02 0:03 ` Ming Lei
2020-02-02 7:05 ` 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=000000000000e76ba6059d926c08@google.com \
--to=syzbot+44c32606d8669fb0d45c@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=dave@stgolabs.net \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ming.lei@redhat.com \
--cc=osandov@fb.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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).