From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: syzbot <syzbot+6a9ff159672dfbb41c95@syzkaller.appspotmail.com>
Cc: ast@kernel.org, aviadye@mellanox.com, borisp@mellanox.com,
bpf@vger.kernel.org, daniel@iogearbox.net, davejwatson@fb.com,
davem@davemloft.net, hdanton@sina.com, john.fastabend@gmail.com,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org
Subject: Re: INFO: task hung in tls_sw_release_resources_tx
Date: Fri, 16 Aug 2019 19:02:34 -0700 [thread overview]
Message-ID: <20190816190234.2aaab5b6@cakuba.netronome.com> (raw)
In-Reply-To: <000000000000e75f1805902bb919@google.com>
On Thu, 15 Aug 2019 11:06:00 -0700, syzbot wrote:
> syzbot has bisected this bug to:
>
> commit 130b392c6cd6b2aed1b7eb32253d4920babb4891
> Author: Dave Watson <davejwatson@fb.com>
> Date: Wed Jan 30 21:58:31 2019 +0000
>
> net: tls: Add tls 1.3 support
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=118e8dee600000
> start commit: 6d5afe20 sctp: fix memleak in sctp_send_reset_streams
> git tree: net
> final crash: https://syzkaller.appspot.com/x/report.txt?x=138e8dee600000
> console output: https://syzkaller.appspot.com/x/log.txt?x=158e8dee600000
> kernel config: https://syzkaller.appspot.com/x/.config?x=a4c9e9f08e9e8960
> dashboard link: https://syzkaller.appspot.com/bug?extid=6a9ff159672dfbb41c95
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17cb0502600000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14d5dc22600000
>
> Reported-by: syzbot+6a9ff159672dfbb41c95@syzkaller.appspotmail.com
> Fixes: 130b392c6cd6 ("net: tls: Add tls 1.3 support")
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
CC Herbert, linux-crypto
This is got to be something in the crypto code :S
The test case opens a ktls socket and back log writes to it.
Then it opens a AF_ALG socket, binds "pcrypt(gcm(aes))" and dies.
The ktls socket upon close waits for async crypto callbacks, but they
never come. If I unset CRYPTO_USER_API_AEAD or change the alg to bind
to "gcm(aes)" the bug does not trigger.
Any suggestions?
next prev parent reply other threads:[~2019-08-17 2:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 10:54 INFO: task hung in tls_sw_release_resources_tx syzbot
2019-08-15 18:06 ` syzbot
2019-08-17 2:02 ` Jakub Kicinski [this message]
2019-08-17 5:47 ` Eric Biggers
2019-08-19 21:12 ` Jakub Kicinski
2019-08-19 21:35 ` Jakub Kicinski
2019-08-21 6:37 ` Steffen Klassert
[not found] <20190815141419.15036-1-hdanton@sina.com>
2019-08-16 1:11 ` 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=20190816190234.2aaab5b6@cakuba.netronome.com \
--to=jakub.kicinski@netronome.com \
--cc=ast@kernel.org \
--cc=aviadye@mellanox.com \
--cc=borisp@mellanox.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davejwatson@fb.com \
--cc=davem@davemloft.net \
--cc=hdanton@sina.com \
--cc=herbert@gondor.apana.org.au \
--cc=john.fastabend@gmail.com \
--cc=linux-crypto@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+6a9ff159672dfbb41c95@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/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).