From: syzbot <syzbot+907b8537e3b0e55151fc@syzkaller.appspotmail.com>
To: bfields@fieldses.org, boqun.feng@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: possible deadlock in send_sigio (2)
Date: Fri, 29 Jan 2021 09:36:07 -0800 [thread overview]
Message-ID: <00000000000079a40e05ba0d702f@google.com> (raw)
In-Reply-To: <000000000000d4b96a05aedda7e2@google.com>
syzbot suspects this issue was fixed by commit:
commit 8d1ddb5e79374fb277985a6b3faa2ed8631c5b4c
Author: Boqun Feng <boqun.feng@gmail.com>
Date: Thu Nov 5 06:23:51 2020 +0000
fcntl: Fix potential deadlock in send_sig{io, urg}()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17455db4d00000
start commit: 7b1b868e Merge tag 'for-linus' of git://git.kernel.org/pub..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=3416bb960d5c705d
dashboard link: https://syzkaller.appspot.com/bug?extid=907b8537e3b0e55151fc
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=163e046b500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12f8b623500000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: fcntl: Fix potential deadlock in send_sig{io, urg}()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2021-01-29 17:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 8:58 possible deadlock in send_sigio (2) syzbot
2020-11-05 4:30 ` syzbot
2020-11-05 6:51 ` syzbot
2021-01-29 17:36 ` syzbot [this message]
2021-02-01 8:03 ` Dmitry Vyukov
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=00000000000079a40e05ba0d702f@google.com \
--to=syzbot+907b8537e3b0e55151fc@syzkaller.appspotmail.com \
--cc=bfields@fieldses.org \
--cc=boqun.feng@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.