From: Jakub Kicinski <kuba@kernel.org>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
Shuah Khan <shuah@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org, Netdev <netdev@vger.kernel.org>
Subject: Re: kselftest: net: tls: hangs
Date: Fri, 25 Mar 2022 16:12:03 -0700 [thread overview]
Message-ID: <20220325161203.7000698c@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <8c81e8ad-6741-b5ed-cf0a-5a302d51d40a@linuxfoundation.org>
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?
next prev parent reply other threads:[~2022-03-25 23:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 7:40 kselftest: net: tls: hangs Naresh Kamboju
2022-03-25 22:13 ` Shuah Khan
2022-03-25 23:12 ` Jakub Kicinski [this message]
2022-03-25 23:34 ` Shuah Khan
2022-03-29 14:49 ` Naresh Kamboju
[not found] ` <20220329102649.507bbf2a@kernel.org>
2022-03-29 17:46 ` Naresh Kamboju
2022-03-29 17:56 ` Jakub Kicinski
2022-03-31 7:48 ` Naresh Kamboju
2022-03-31 18:54 ` Jakub Kicinski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220325161203.7000698c@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).