[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <00000000000079a40e05ba0d702f@google.com>
Date: Fri, 29 Jan 2021 09:36:07 -0800
From: syzbot <syzbot+907b8537e3b0e55151fc@...kaller.appspotmail.com>
To: bfields@...ldses.org, boqun.feng@...il.com, jlayton@...nel.org,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
mingo@...hat.com, peterz@...radead.org,
syzkaller-bugs@...glegroups.com, viro@...iv.linux.org.uk,
will@...nel.org
Subject: Re: possible deadlock in send_sigio (2)
syzbot suspects this issue was fixed by commit:
commit 8d1ddb5e79374fb277985a6b3faa2ed8631c5b4c
Author: Boqun Feng <boqun.feng@...il.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
Powered by blists - more mailing lists