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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 25 Mar 2022 17:34:27 -0600 From: Shuah Khan <skhan@...uxfoundation.org> To: Jakub Kicinski <kuba@...nel.org> Cc: Naresh Kamboju <naresh.kamboju@...aro.org>, Shuah Khan <shuah@...nel.org>, "David S. Miller" <davem@...emloft.net>, Paolo Abeni <pabeni@...hat.com>, Linux-Next Mailing List <linux-next@...r.kernel.org>, "open list:KERNEL SELFTEST FRAMEWORK" <linux-kselftest@...r.kernel.org>, open list <linux-kernel@...r.kernel.org>, lkft-triage@...ts.linaro.org, Netdev <netdev@...r.kernel.org>, Shuah Khan <skhan@...uxfoundation.org> Subject: Re: kselftest: net: tls: hangs On 3/25/22 5:12 PM, Jakub Kicinski wrote: > On Fri, 25 Mar 2022 16:13:33 -0600 Shuah Khan wrote: >>> # # RUN tls.13_sm4_gcm.splice_cmsg_to_pipe ... >>> # # tls.c:688:splice_cmsg_to_pipe:Expected splice(self->cfd, NULL, >>> p[1], NULL, send_len, 0) (10) == -1 (-1) >>> # # tls.c:689:splice_cmsg_to_pipe:Expected errno (2) == EINVAL (22) >>> # # splice_cmsg_to_pipe: Test terminated by timeout >>> # # FAIL tls.13_sm4_gcm.splice_cmsg_to_pipe >>> # not ok 217 tls.13_sm4_gcm.splice_cmsg_to_pipe >>> # # RUN tls.13_sm4_gcm.splice_dec_cmsg_to_pipe ... >>> # # tls.c:708:splice_dec_cmsg_to_pipe:Expected recv(self->cfd, buf, >>> send_len, 0) (10) == -1 (-1) >>> # # tls.c:709:splice_dec_cmsg_to_pipe:Expected errno (2) == EIO (5) >>> [ 661.901558] kworker/dying (49) used greatest stack depth: 10576 bytes left >> >> This seems to be the problem perhaps. >> >> Jakub, any thoughts. The last change to tls.c was a while back. > > Yes, sorry, kicked off a build and got distracted. > > I can repro the failures, TLS=n in the config I must have not tested > that in the new cases. > > But I can't repro the hung, and we have a timer at the hardness level > IIUC so IDK how this could "hang"? > > Naresh, is there any stack trace in the logs? Can you repro on Linus's > tree? > I couldn't reproduce this either - I have TLS=m thanks, -- Shuah
Powered by blists - more mailing lists