From: Dmitry Vyukov <dvyukov@google.com>
To: syzbot <syzbot+ae82084b07d0297e566b@syzkaller.appspotmail.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
overlayfs <linux-unionfs@vger.kernel.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Cc: Amir Goldstein <amir73il@gmail.com>
Subject: Re: possible deadlock in mnt_want_write
Date: Wed, 11 Nov 2020 14:52:05 +0100 [thread overview]
Message-ID: <CACT4Y+Z=WF1jbjjSX0hWSJXqUpNGJgwW=f2tBFkJH=mSjyMqag@mail.gmail.com> (raw)
In-Reply-To: <000000000000ad052105b383350a@google.com>
On Sat, Nov 7, 2020 at 1:10 PM syzbot
<syzbot+ae82084b07d0297e566b@syzkaller.appspotmail.com> wrote:
>
> syzbot suspects this issue was fixed by commit:
>
> commit 146d62e5a5867fbf84490d82455718bfb10fe824
> Author: Amir Goldstein <amir73il@gmail.com>
> Date: Thu Apr 18 14:42:08 2019 +0000
>
> ovl: detect overlapping layers
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11e40184500000
> start commit: 6d906f99 Merge tag 'arm64-fixes' of git://git.kernel.org/p..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=856fc6d0fbbeede9
> dashboard link: https://syzkaller.appspot.com/bug?extid=ae82084b07d0297e566b
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=111767b7200000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1611ab2d200000
>
> If the result looks correct, please mark the issue as fixed by replying with:
>
> #syz fix: ovl: detect overlapping layers
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
#syz fix: ovl: detect overlapping layers
prev parent reply other threads:[~2020-11-11 13:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000d03eea0571adfe83@google.com>
2019-11-23 2:27 ` possible deadlock in mnt_want_write syzbot
2020-11-07 12:10 ` syzbot
2020-11-11 13:52 ` Dmitry Vyukov [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='CACT4Y+Z=WF1jbjjSX0hWSJXqUpNGJgwW=f2tBFkJH=mSjyMqag@mail.gmail.com' \
--to=dvyukov@google.com \
--cc=amir73il@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=syzbot+ae82084b07d0297e566b@syzkaller.appspotmail.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).