From: Jens Axboe <axboe@kernel.dk>
To: syzbot <syzbot+6e8f5b555cce8fac0423@syzkaller.appspotmail.com>,
christian@brauner.io, ebiederm@xmission.com,
io-uring@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, liuzhiqiang26@huawei.com,
oleg@redhat.com, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk
Subject: Re: possible deadlock in __lock_task_sighand
Date: Sat, 29 Aug 2020 18:34:11 -0600 [thread overview]
Message-ID: <d104d06a-393e-0d47-ef6d-2f1010c9c2b3@kernel.dk> (raw)
In-Reply-To: <0000000000001bdf9705ae0d151b@google.com>
This is already fixed, and it went upstream yesterday.
#syz fix: io_uring: don't recurse on tsk->sighand->siglock with signalfd
--
Jens Axboe
prev parent reply other threads:[~2020-08-30 0:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-30 0:08 possible deadlock in __lock_task_sighand syzbot
2020-08-30 0:34 ` Jens Axboe [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=d104d06a-393e-0d47-ef6d-2f1010c9c2b3@kernel.dk \
--to=axboe@kernel.dk \
--cc=christian@brauner.io \
--cc=ebiederm@xmission.com \
--cc=io-uring@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuzhiqiang26@huawei.com \
--cc=oleg@redhat.com \
--cc=syzbot+6e8f5b555cce8fac0423@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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