linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+a50c7541a4a55cd49b02@syzkaller.appspotmail.com>
To: aarcange@redhat.com, adilger.kernel@dilger.ca,
	akpm@linux-foundation.org, aneesh.kumar@linux.vnet.ibm.com,
	dave@stgolabs.net, davem@davemloft.net, hughd@google.com,
	jiangshanlai@gmail.com, kirill.shutemov@linux.intel.com,
	kuznet@ms2.inr.ac.ru, linux-ext4@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	mhocko@kernel.org, mike.kravetz@oracle.com,
	n-horiguchi@ah.jp.nec.com, netdev@vger.kernel.org,
	prakash.sangappa@oracle.com, sbrivio@redhat.com,
	sd@queasysnail.net, syzkaller-bugs@googlegroups.com,
	tj@kernel.org, torvalds@linux-foundation.org, tytso@mit.edu,
	viro@zeniv.linux.org.uk, yoshfuji@linux-ipv6.org
Subject: Re: possible deadlock in flush_workqueue (2)
Date: Thu, 07 Nov 2019 05:42:07 -0800	[thread overview]
Message-ID: <000000000000d8b0630596c1d4a0@google.com> (raw)
In-Reply-To: <000000000000bfd4270578abe88b@google.com>

syzbot suspects this bug was fixed by commit:

commit e7c58097793ef15d58fadf190ee58738fbf447cd
Author: Mike Kravetz <mike.kravetz@oracle.com>
Date:   Tue Jan 8 23:23:32 2019 +0000

     hugetlbfs: revert "Use i_mmap_rwsem to fix page fault/truncate race"

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=14ec0d2c600000
start commit:   ca9eb48f Merge tag 'regulator-v5.0' of git://git.kernel.or..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=963b24abf3f7c2d8
dashboard link: https://syzkaller.appspot.com/bug?extid=a50c7541a4a55cd49b02
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=12097f03400000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=10b55ac5400000

If the result looks correct, please mark the bug fixed by replying with:

#syz fix: hugetlbfs: revert "Use i_mmap_rwsem to fix page fault/truncate  
race"

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

      parent reply	other threads:[~2019-11-07 13:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <000000000000bfd4270578abe88b@google.com>
     [not found] ` <0000000000009bcd4a0578e22ebd@google.com>
2018-10-23 14:28   ` possible deadlock in flush_workqueue (2) Theodore Y. Ts'o
2018-10-23 19:40     ` Tejun Heo
2019-03-22 11:12 ` syzbot
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=000000000000d8b0630596c1d4a0@google.com \
    --to=syzbot+a50c7541a4a55cd49b02@syzkaller.appspotmail.com \
    --cc=aarcange@redhat.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=akpm@linux-foundation.org \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=dave@stgolabs.net \
    --cc=davem@davemloft.net \
    --cc=hughd@google.com \
    --cc=jiangshanlai@gmail.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhocko@kernel.org \
    --cc=mike.kravetz@oracle.com \
    --cc=n-horiguchi@ah.jp.nec.com \
    --cc=netdev@vger.kernel.org \
    --cc=prakash.sangappa@oracle.com \
    --cc=sbrivio@redhat.com \
    --cc=sd@queasysnail.net \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tj@kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=tytso@mit.edu \
    --cc=viro@zeniv.linux.org.uk \
    --cc=yoshfuji@linux-ipv6.org \
    /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).