From: syzbot <syzbot+8073030e235a5a84dd31@syzkaller.appspotmail.com>
To: asm@florahospitality.com, bfields@fieldses.org,
boqun.feng@gmail.com, desmondcheongzx@gmail.com,
jlayton@kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, mingo@redhat.com,
peterz@infradead.org, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk, will@kernel.org
Subject: Re: [syzbot] possible deadlock in f_getown
Date: Wed, 22 Sep 2021 23:03:14 -0700 [thread overview]
Message-ID: <000000000000ed2e6705cca36282@google.com> (raw)
In-Reply-To: <000000000000bf710a05b05ae3f6@google.com>
syzbot suspects this issue was fixed by commit:
commit f671a691e299f58835d4660d642582bf0e8f6fda
Author: Desmond Cheong Zhi Xi <desmondcheongzx@gmail.com>
Date: Fri Jul 2 09:18:30 2021 +0000
fcntl: fix potential deadlocks for &fown_struct.lock
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15fa8017300000
start commit: 293837b9ac8d Revert "i915: fix remap_io_sg to verify the p..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=18fade5827eb74f7
dashboard link: https://syzkaller.appspot.com/bug?extid=8073030e235a5a84dd31
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=171390add00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10050553d00000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: fcntl: fix potential deadlocks for &fown_struct.lock
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2021-09-23 6:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 7:48 possible deadlock in f_getown syzbot
2020-11-30 12:39 ` syzbot
2020-11-30 19:23 ` syzbot
2021-09-23 6:03 ` syzbot [this message]
2021-09-23 17:20 ` [syzbot] " Desmond Cheong Zhi Xi
2021-09-23 17:54 ` Jeff Layton
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=000000000000ed2e6705cca36282@google.com \
--to=syzbot+8073030e235a5a84dd31@syzkaller.appspotmail.com \
--cc=asm@florahospitality.com \
--cc=bfields@fieldses.org \
--cc=boqun.feng@gmail.com \
--cc=desmondcheongzx@gmail.com \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
--cc=will@kernel.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).