linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+148c2885d71194f18d28@syzkaller.appspotmail.com>
To: arve@android.com, devel@driverdev.osuosl.org, dvyukov@google.com,
	ebiggers3@gmail.com, gregkh@linuxfoundation.org,
	joelaf@google.com, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, maco@android.com,
	penguin-kernel@i-love.sakura.ne.jp,
	syzkaller-bugs@googlegroups.com, tkjos@android.com,
	tkjos@google.com
Subject: Re: possible deadlock in vfs_fallocate
Date: Tue, 22 Jan 2019 06:26:03 -0800	[thread overview]
Message-ID: <000000000000d6738b05800cc19e@google.com> (raw)
In-Reply-To: <CACT4Y+YNgYqynkhv7DMCCkO+xFebrpWfTXwdyeYsN=RkWmLiYw@mail.gmail.com>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger  
crash:

Reported-and-tested-by:  
syzbot+148c2885d71194f18d28@syzkaller.appspotmail.com

Tested on:

commit:         48b161983ae5 Merge tag 'xarray-5.0-rc3' of git://git.infra..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=dd3a020d055fa2e8
compiler:       gcc (GCC) 9.0.0 20181231 (experimental)
patch:          https://syzkaller.appspot.com/x/patch.diff?x=16e6d908c00000

Note: testing is done by a robot and is best-effort only.

      reply	other threads:[~2019-01-22 14:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-29 17:00 possible deadlock in vfs_fallocate syzbot
2018-05-09  7:57 ` Eric Biggers
     [not found]   ` <CAHRSSEwAjrxZLRa3tPhjvz2MFiqVbCysTTgp6oKc=3Pcr1b2JQ@mail.gmail.com>
2019-01-22 13:58     ` Dmitry Vyukov
2019-01-22 14:26       ` 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=000000000000d6738b05800cc19e@google.com \
    --to=syzbot+148c2885d71194f18d28@syzkaller.appspotmail.com \
    --cc=arve@android.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=dvyukov@google.com \
    --cc=ebiggers3@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=joelaf@google.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maco@android.com \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tkjos@android.com \
    --cc=tkjos@google.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).