Re: possible deadlock in __lock_task_sighand

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: syzbot <syzbot+6e8f5b555cce8fac0423@xxxxxxxxxxxxxxxxxxxxxxxxx>, christian@xxxxxxxxxx, ebiederm@xxxxxxxxxxxx, io-uring@xxxxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, liuzhiqiang26@xxxxxxxxxx, oleg@xxxxxxxxxx, syzkaller-bugs@xxxxxxxxxxxxxxxx, viro@xxxxxxxxxxxxxxxxxx
Subject: Re: possible deadlock in __lock_task_sighand
From: Jens Axboe <axboe@xxxxxxxxx>
Date: Sat, 29 Aug 2020 18:34:11 -0600
In-reply-to: <0000000000001bdf9705ae0d151b@google.com>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0

This is already fixed, and it went upstream yesterday.

#syz fix: io_uring: don't recurse on tsk->sighand->siglock with signalfd

-- 
Jens Axboe

References:
- possible deadlock in __lock_task_sighand
  - From: syzbot

Prev by Date: possible deadlock in __lock_task_sighand
Next by Date: [PATCH] fat: Avoid oops when bdi->io_pages==0
Previous by thread: possible deadlock in __lock_task_sighand
Next by thread: [PATCH] fat: Avoid oops when bdi->io_pages==0
Index(es):
- Date
- Thread

[Index of Archives] [Linux Ext4 Filesystem] [Union Filesystem] [Filesystem Testing] [Ceph Users] [Ecryptfs] [AutoFS] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Cachefs] [Reiser Filesystem] [Linux RAID] [Samba] [Device Mapper] [CEPH Development]

Powered by Linux