Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   mdecandia@gmail.com
To:     gregkh@linuxfoundation.org
Cc:     akpm@linux-foundation.org, bsegall@google.com, edumazet@google.com,
        jbaron@akamai.com, khazhy@google.com, linux-kernel@vger.kernel.org,
        r@hev.cc, rpenyaev@suse.de, shakeelb@google.com, stable@kernel.org,
        stable@vger.kernel.org, torvalds@linux-foundation.org,
        viro@zeniv.linux.org.uk
Subject: [PATCH 5.4 051/389] epoll: autoremove wakers even more aggressively
Date:   Wed, 26 Oct 2022 18:00:51 +0200
Message-Id: <20221026160051.5340-1-mdecandia@gmail.com>
In-Reply-To: <20220823080117.738248512@linuxfoundation.org>
References: <20220823080117.738248512@linuxfoundation.org>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

=0D
Subject: [PATCH 5.4 051/389] epoll: autoremove wakers even more aggressivel=
y=0D
=0D
Hi all,=0D
I'm facing an hangup of runc command during startup of containers on Ubuntu=
 20.04,=0D
just adding this patch to my updated linux kernel 5.4.210.=0D
=0D
The runc process exits if I run an strace on it with the strace_runc_hangup=
.login you can find here=0D
=0D
https://github.com/opencontainers/runc/issues/3641=0D
=0D
with more details.=0D
=0D
Testing it with previous docker-ce/containerio releases, just hangup the ru=
nc process and it will remain locked even analyzing it with strace.=0D
=0D
Any idea or further test I can do on it?=0D
=0D
Thanks,=0D
Michele=