From: syzbot <syzbot+5cd33f0e6abe2bb3e397@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, torvalds@linux-foundation.org,
tytso@mit.edu, viro@zeniv.linux.org.uk
Subject: Re: possible deadlock in __generic_file_fsync
Date: Fri, 22 Mar 2019 14:28:01 -0700 [thread overview]
Message-ID: <00000000000088ea3e0584b5872d@google.com> (raw)
In-Reply-To: <000000000000cd1e2205785951c2@google.com>
syzbot has bisected this bug to:
commit 9022ada8ab6f1f1a932a3c93815061042e6548a5
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Fri Aug 24 20:16:36 2018 +0000
Merge branch 'for-4.19' of
git://git.kernel.org/pub/scm/linux/kernel/git/tj/wq
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15330437200000
start commit: 270b77a0 Merge tag 'drm-fixes-2018-10-20-1' of git://anong..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=17330437200000
console output: https://syzkaller.appspot.com/x/log.txt?x=13330437200000
kernel config: https://syzkaller.appspot.com/x/.config?x=b3f55cb3dfcc6c33
dashboard link: https://syzkaller.appspot.com/bug?extid=5cd33f0e6abe2bb3e397
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1436fc45400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11058e2d400000
Reported-by: syzbot+5cd33f0e6abe2bb3e397@syzkaller.appspotmail.com
Fixes: 9022ada8ab6f ("Merge branch 'for-4.19' of
git://git.kernel.org/pub/scm/linux/kernel/git/tj/wq")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-03-22 21:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 14:25 possible deadlock in __generic_file_fsync syzbot
2018-10-19 2:10 ` syzbot
2018-10-20 16:13 ` syzbot
2019-03-22 21:28 ` syzbot [this message]
2019-03-23 7:16 ` Dmitry Vyukov
2019-03-23 13:56 ` Theodore Ts'o
2019-03-26 10:32 ` Dmitry Vyukov
2020-03-08 5:52 ` [PATCH] fs/direct-io.c: avoid workqueue allocation race Eric Biggers
2020-03-08 23:12 ` Dave Chinner
2020-03-09 1:24 ` Eric Biggers
2020-03-10 16:27 ` Darrick J. Wong
2020-03-10 22:22 ` Dave Chinner
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=00000000000088ea3e0584b5872d@google.com \
--to=syzbot+5cd33f0e6abe2bb3e397@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--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).