Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp71989ybl; Fri, 16 Aug 2019 19:03:27 -0700 (PDT) X-Google-Smtp-Source: APXvYqwHNpC9x46ySeXNMuP0eWC5+IQ8+YhS+2nb61TKV1g8r90vrwLysmEWeEVzyCFXkK7SYRXB X-Received: by 2002:a63:2a41:: with SMTP id q62mr3929696pgq.444.1566007406894; Fri, 16 Aug 2019 19:03:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566007406; cv=none; d=google.com; s=arc-20160816; b=WaKRGawk9SEvCT7mwU9gA/p1tPL2O9gMaDlo8MBWtSeeBZqHPk0LTwzhc+ky588wCd ksl9+Cl4Fzt0Cm3MMgvTXqM6A7rTwFQRReccvnU0cAMtMV/tKk/7RfZBgtljx6jQZSAR ZIveK9Re3f3NVa3sxTp4Uw2+Wq6FKC7Io44nHJ+/HVUqJADHGrpQcqViUybvYEsSzq1i kSUnVnj+Xu+IPWg01SAGKxa1v0XSQwjTZQx4zNBM2d92NIPeDLSkrmaO9+kqZOn0+C5c hnszKP/TkTewHttmmgXOPn642n4fLZvan2FkB7vxGSIrMnqy+Ly/f86dSjg3Q1zkZv3L MbgQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date:dkim-signature; bh=x7XMRdgCt2pdutYjeOA8x9Ig7Wjm5vmCkdNaXQUT6Gk=; b=sr0+JlDPc0P1ildeUNrO5btK12PpJu5kc1/fVujMh+uucvPwqGczTqSL12Elsjif14 +h/MDTddplaYhjYB4Ejnz4Jcah6XQQeQvQGJYoOGXTJ7YZTKDAYBdehV7LkNpNPLHuxj 7oZdsIGhErgPvNkQ2bdzLfLfFqSBbBZXhPdt5IcMHwlABmTyuotbUkifJK+KR0z4g1yB QnE98aXJXotIFqqGS8xEf/qnJDNyP3j+lqlGPnn99vZoQiArtXGecLB3lzrdh2nX+OGS 48wIlYlvS35u+SHjq4zBQX3sJLL69O90j15LlYSb21UHJQpG158iwkACdzoe+U1kM0oS 0mwA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@netronome-com.20150623.gappssmtp.com header.s=20150623 header.b="mcrBVju/"; spf=pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v41si4968876pgn.481.2019.08.16.19.03.01; Fri, 16 Aug 2019 19:03:26 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@netronome-com.20150623.gappssmtp.com header.s=20150623 header.b="mcrBVju/"; spf=pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726023AbfHQCCy (ORCPT + 99 others); Fri, 16 Aug 2019 22:02:54 -0400 Received: from mail-qk1-f194.google.com ([209.85.222.194]:44362 "EHLO mail-qk1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725911AbfHQCCy (ORCPT ); Fri, 16 Aug 2019 22:02:54 -0400 Received: by mail-qk1-f194.google.com with SMTP id d79so6260106qke.11 for ; Fri, 16 Aug 2019 19:02:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netronome-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :organization:mime-version:content-transfer-encoding; bh=x7XMRdgCt2pdutYjeOA8x9Ig7Wjm5vmCkdNaXQUT6Gk=; b=mcrBVju/QdoZkaoB86phY6BSIh7IESknpTqtDe3XtRMD7Xy5pTRaU/N/J6F9daxjdq NniNEg5UUDIRIyZRt6UbPX+niko9VyYxxbJkBKgKe2XjuQ2qa0MhDcp6DhrTnqIT1hfz 0EnzaX0R/41+BqO0OORepLUzJRBtkQIMPMwDmQ2XcvBARvt65s0fPrzSa75czg8a2q0q FVfM/RNjC5wMHXa1y7p5xTYzjBwIFKm1bDVMqZKQfaxq1KHdcjmJ4DdSH1Pug46UhQNm MF0BUzCsTKr9cxRJhrBFIxt0IHsAdQvJy3FLykz5j4PUGQrH8Ekm4lzrHGmlnQ7n9JGB FrCg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:organization:mime-version:content-transfer-encoding; bh=x7XMRdgCt2pdutYjeOA8x9Ig7Wjm5vmCkdNaXQUT6Gk=; b=gRUgdsixy7K8peB0qukLi/HzYeHjEkfYljJfrWDzDG12PI8qWxxcoK9kzpVur9nLR/ GfdGoDA3mPs5YXDvTpOs9b2gMl5m/npb8UtaGcFlGIAKXBqB0zu7gg17RexDFWoz3r7p TrOoO0JI/HWEYdkAhXLBVId0IjK1Z8cRTgGfpPtnw5BLB6OgyPVJ4urRFZb0iQTXhrvW RbqgEOY7zo2EtKLhfKy22b0oBleOyGxdxnmOHcJQVgSYOgAEO5p0eUD92HLJuURRtiA2 AQ6G6Kf4f/ui0sPOqwmI0tmqVYvSJhhdLAy6JatxvaMr2EKC2+wate63WlWC84D/I2CJ TfxA== X-Gm-Message-State: APjAAAUu33vUNXFWpJSlj36bgVQ5wq6ExDfQ4G4od/n8ryi8SQNClnx+ c1l/usfnRw3gruo71GszmLoOWw== X-Received: by 2002:a05:620a:1355:: with SMTP id c21mr10818956qkl.97.1566007373239; Fri, 16 Aug 2019 19:02:53 -0700 (PDT) Received: from cakuba.netronome.com ([66.60.152.14]) by smtp.gmail.com with ESMTPSA id x145sm1678748qka.106.2019.08.16.19.02.51 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 16 Aug 2019 19:02:53 -0700 (PDT) Date: Fri, 16 Aug 2019 19:02:34 -0700 From: Jakub Kicinski To: syzbot 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 Message-ID: <20190816190234.2aaab5b6@cakuba.netronome.com> In-Reply-To: <000000000000e75f1805902bb919@google.com> References: <000000000000523ea3059025b11d@google.com> <000000000000e75f1805902bb919@google.com> Organization: Netronome Systems, Ltd. MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-crypto-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org On Thu, 15 Aug 2019 11:06:00 -0700, syzbot wrote: > syzbot has bisected this bug to: > > commit 130b392c6cd6b2aed1b7eb32253d4920babb4891 > Author: Dave Watson > 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?