linux-kernel - Re: possible deadlock in __lock_task

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <d104d06a-393e-0d47-ef6d-2f1010c9c2b3@kernel.dk>
Date:   Sat, 29 Aug 2020 18:34:11 -0600
From:   Jens Axboe <axboe@...nel.dk>
To:     syzbot <syzbot+6e8f5b555cce8fac0423@...kaller.appspotmail.com>,
        christian@...uner.io, ebiederm@...ssion.com,
        io-uring@...r.kernel.org, linux-fsdevel@...r.kernel.org,
        linux-kernel@...r.kernel.org, liuzhiqiang26@...wei.com,
        oleg@...hat.com, syzkaller-bugs@...glegroups.com,
        viro@...iv.linux.org.uk
Subject: Re: possible deadlock in __lock_task_sighand

This is already fixed, and it went upstream yesterday.

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

-- 
Jens Axboe