From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id F17B9C433E1 for ; Fri, 5 Jun 2020 14:10:58 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id C8FD620820 for ; Fri, 5 Jun 2020 14:10:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1591366258; bh=6CAvZuBjeBM0ZEQzjCvTEjempo7YDRIo6woMgR5VCTc=; h=Date:From:To:To:To:CC:Cc:Cc:Cc:Cc:Cc:Cc:Cc:Cc:Cc:Subject: In-Reply-To:List-ID:From; b=rWvLt+kTeaWGc+gOeaqtZxIy3a2NLBkjR0fVBQao7gCDGwYNE4jqOwXfDacciMhD/ LVfhJaxPXEPVSlCAO2/ZTBxQ5psozm5e3XdoDfBw3tZ08wG7WQYrThagJhiR41VIb7 ccOwvnPEypU2xgLw6DE1m0Lh+1jFuvUygImqSJ0E= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728056AbgFEOK5 (ORCPT ); Fri, 5 Jun 2020 10:10:57 -0400 Received: from mail.kernel.org ([198.145.29.99]:41756 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728025AbgFEOKw (ORCPT ); Fri, 5 Jun 2020 10:10:52 -0400 Received: from localhost (unknown [137.135.114.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id BAE3D207D8; Fri, 5 Jun 2020 14:10:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1591366251; bh=6CAvZuBjeBM0ZEQzjCvTEjempo7YDRIo6woMgR5VCTc=; h=Date:From:To:To:To:CC:Cc:Cc:Cc:Cc:Cc:Cc:Cc:Cc:Cc:Subject: In-Reply-To:From; b=fho5hoZlTyKUsdCwJCGiQwIPyo9Gh8DAvxPiSiLTEPMwovO2eb4MQJuVdQ/nnwY6V duSjOxxv77vhW972j5zek6sE2ow+C2tR7BE4bMCHwGhl2W9y5BdyusDXcVZcXbRAjj BICurL4ZW38BM5gDWohKVnSN8egvpb8q40c8dX/g= Date: Fri, 05 Jun 2020 14:10:51 +0000 From: Sasha Levin To: Sasha Levin To: "Longpeng(Mike)" To: CC: "Longpeng(Mike)" Cc: Gonglei Cc: Herbert Xu Cc: "Michael S. Tsirkin" Cc: Jason Wang Cc: "David S. Miller" Cc: virtualization@lists.linux-foundation.org Cc: linux-kernel@vger.kernel.org Cc: stable@vger.kernel.org Cc: stable@vger.kernel.org Subject: Re: [PATCH v3 2/3] crypto: virtio: Fix use-after-free in virtio_crypto_skcipher_finalize_req() In-Reply-To: <20200602070501.2023-3-longpeng2@huawei.com> Message-Id: <20200605141051.BAE3D207D8@mail.kernel.org> Sender: linux-crypto-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org <20200123101000.GB24255@Red> References: <20200602070501.2023-3-longpeng2@huawei.com> <20200123101000.GB24255@Red> Hi [This is an automated email] This commit has been processed because it contains a "Fixes:" tag fixing commit: dbaf0624ffa5 ("crypto: add virtio-crypto driver"). The bot has tested the following trees: v5.6.15, v5.4.43, v4.19.125, v4.14.182. v5.6.15: Build OK! v5.4.43: Failed to apply! Possible dependencies: eee1d6fca0a0 ("crypto: virtio - switch to skcipher API") v4.19.125: Failed to apply! Possible dependencies: eee1d6fca0a0 ("crypto: virtio - switch to skcipher API") v4.14.182: Failed to apply! Possible dependencies: 500e6807ce93 ("crypto: virtio - implement missing support for output IVs") 67189375bb3a ("crypto: virtio - convert to new crypto engine API") d0d859bb87ac ("crypto: virtio - Register an algo only if it's supported") e02b8b43f55a ("crypto: virtio - pr_err() strings should end with newlines") eee1d6fca0a0 ("crypto: virtio - switch to skcipher API") NOTE: The patch will not be queued to stable trees until it is upstream. How should we proceed with this patch? -- Thanks Sasha From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sasha Levin Subject: Re: [PATCH v3 2/3] crypto: virtio: Fix use-after-free in virtio_crypto_skcipher_finalize_req() Date: Fri, 05 Jun 2020 14:10:51 +0000 Message-ID: <20200605141051.BAE3D207D8@mail.kernel.org> References: <20200602070501.2023-3-longpeng2@huawei.com> Return-path: In-Reply-To: <20200602070501.2023-3-longpeng2@huawei.com> Sender: linux-crypto-owner@vger.kernel.org To: Sasha Levin , linux-crypto@vger.kernel.org Cc: "Longpeng(Mike)" , Gonglei , Herbert Xu , "Michael S. Tsirkin" , Jason Wang , "David S. Miller" , virtualization@lists.linux-foundation.org, linux-kernel@vger.kernel.org, stable@vger.kernel.orgstable@vger.kernel.org List-Id: virtualization@lists.linuxfoundation.org <20200123101000.GB24255@Red> References: <20200602070501.2023-3-longpeng2@huawei.com> <20200123101000.GB24255@Red> Hi [This is an automated email] This commit has been processed because it contains a "Fixes:" tag fixing commit: dbaf0624ffa5 ("crypto: add virtio-crypto driver"). The bot has tested the following trees: v5.6.15, v5.4.43, v4.19.125, v4.14.182. v5.6.15: Build OK! v5.4.43: Failed to apply! Possible dependencies: eee1d6fca0a0 ("crypto: virtio - switch to skcipher API") v4.19.125: Failed to apply! Possible dependencies: eee1d6fca0a0 ("crypto: virtio - switch to skcipher API") v4.14.182: Failed to apply! Possible dependencies: 500e6807ce93 ("crypto: virtio - implement missing support for output IVs") 67189375bb3a ("crypto: virtio - convert to new crypto engine API") d0d859bb87ac ("crypto: virtio - Register an algo only if it's supported") e02b8b43f55a ("crypto: virtio - pr_err() strings should end with newlines") eee1d6fca0a0 ("crypto: virtio - switch to skcipher API") NOTE: The patch will not be queued to stable trees until it is upstream. How should we proceed with this patch? -- Thanks Sasha