linux-kernel - [PATCH 5.4 051/389] epoll: autoremove wakers even more aggressively

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <20221026160051.5340-1-mdecandia@gmail.com>
Date:   Wed, 26 Oct 2022 18:00:51 +0200
From:   mdecandia@...il.com
To:     gregkh@...uxfoundation.org
Cc:     akpm@...ux-foundation.org, bsegall@...gle.com, edumazet@...gle.com,
        jbaron@...mai.com, khazhy@...gle.com, linux-kernel@...r.kernel.org,
        r@....cc, rpenyaev@...e.de, shakeelb@...gle.com, stable@...nel.org,
        stable@...r.kernel.org, torvalds@...ux-foundation.org,
        viro@...iv.linux.org.uk
Subject: [PATCH 5.4 051/389] epoll: autoremove wakers even more aggressively


Subject: [PATCH 5.4 051/389] epoll: autoremove wakers even more aggressively

Hi all,
I'm facing an hangup of runc command during startup of containers on Ubuntu 20.04,
just adding this patch to my updated linux kernel 5.4.210.

The runc process exits if I run an strace on it with the strace_runc_hangup.login you can find here

https://github.com/opencontainers/runc/issues/3641

with more details.

Testing it with previous docker-ce/containerio releases, just hangup the runc process and it will remain locked even analyzing it with strace.

Any idea or further test I can do on it?

Thanks,
Michele