From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 58428241680; Wed, 9 Jul 2025 19:27:34 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1752089255; cv=none; b=qD7VAHFdqfq5gLSYkKoBG50Nt3zTN3Su5kWZG6sbg3hs0ZZRu+PgVAJHEfeW+SUNB1YA3pfuQWCQfwN9VIbG7x3cRgUNdabl+0QrMLA8oWjJY9YpuHwnrjGFQXBlme8+P0O8rSg43KU/l7lGtaQtCsSXC8WtjKBPjwAbQ7nATGg= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1752089255; c=relaxed/simple; bh=Zm+FZCamXFOfYZVRCK0BZ5RTFEHBxsMTaWL62PvvIec=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=oQj2v7nKNM7qI3gI5owYTb7RjPawhkQW5vEilOdBABWOa+UWNLAkmZIV3rLUGUVXTRHS6H50wii6ikv9r0jJZEElL4+6/nc4X+rdnMqMT7zrpdWTtyq1bJG2tlQ/TZNM6h8IcP7N2Qo45vISxhLitUJJsDymjpMcvDLda06P81c= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=tPpKm1td; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="tPpKm1td" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 61672C4CEEF; Wed, 9 Jul 2025 19:27:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1752089254; bh=Zm+FZCamXFOfYZVRCK0BZ5RTFEHBxsMTaWL62PvvIec=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=tPpKm1tdvE3ARsw+TSv1uypiy1hysiratTvCWm6vUTCuPzCxYQG6Fxd+hiYAaZxTf 10aHeuPAJyFJrwqjOLVTOh+uXYVA9Xka5uOBboT312UEjfa45Lop/Qwh4VNxv2B/6g i2nmJnQkX3guMBfi/dvMWsPpiQ5ac8ORB3lf4OcGGOq5VrY5LwkXdoKOCI1ejRerNK 7q1dhRLxF4MvQmBBB/rBRDvcWjMagYnHI5DewDrgLechb1Axm60uYJ0KEM1BN5pY1Y nlhcbGe+TuqG/3l1hQN5ZLl3/fTnwJImeh7zL9ru3SGV6tVAxddg94N7Qd88KxndEs GgfY895mRO6iQ== Date: Wed, 9 Jul 2025 12:26:50 -0700 From: Eric Biggers To: fsverity@lists.linux.dev Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, linux-btrfs@vger.kernel.org, Ard Biesheuvel , "Jason A . Donenfeld" , Theodore Ts'o Subject: Re: [PATCH 0/2] Convert fs/verity/ to use SHA-2 library API Message-ID: <20250709192650.GB28537@sol> References: <20250630172224.46909-1-ebiggers@kernel.org> Precedence: bulk X-Mailing-List: fsverity@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20250630172224.46909-1-ebiggers@kernel.org> On Mon, Jun 30, 2025 at 10:22:22AM -0700, Eric Biggers wrote: > This series, including all its prerequisites, is also available at: > > git fetch https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git fsverity-libcrypto-v1 > > This series makes fs/verity/ use the SHA-2 library API instead of the > old-school crypto API. This is simpler and more efficient. > > This depends on my SHA-2 library improvements for 6.17 (many patches), > so this patchset might need to wait until 6.18. But I'm also thinking > about just basing the fsverity tree on libcrypto-next for 6.17. > > Eric Biggers (2): > lib/crypto: hash_info: Move hash_info.c into lib/crypto/ > fsverity: Switch from crypto_shash to SHA-2 library FYI, I've applied this series to https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git/log/?h=libcrypto-next so that it gets linux-next coverage. As mentioned, it depends on the SHA-256 and SHA-512 improvements in lib/crypto/. But Linus has also expressed a preference to not put too much in one pull request. My current plan is to do 3 pull requests: 1. "Crypto library updates" - most patches, mainly SHA-256 and SHA-512 library improvements 2. "Crypto library tests" - based on (1) but adds: lib/crypto: tests: Add hash-test-template.h and gen-hash-testvecs.py lib/crypto: tests: Add KUnit tests for SHA-224 and SHA-256 lib/crypto: tests: Add KUnit tests for SHA-384 and SHA-512 lib/crypto: tests: Add KUnit tests for Poly1305 3. "Crypto library conversions" - based on (1) but adds: apparmor: use SHA-256 library API instead of crypto_shash API fsverity: Explicitly include fsverity: Switch from crypto_shash to SHA-2 library I'll put all of these in libcrypto-next for linux-next coverage, but (3) will have a slightly different base commit in the final version. - Eric 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 Received: from lists.sourceforge.net (lists.sourceforge.net [216.105.38.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id D66C4C83F0A for ; Wed, 9 Jul 2025 19:27:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.sourceforge.net; s=beta; h=Content-Transfer-Encoding:Content-Type:Cc: Reply-To:From:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:Subject:In-Reply-To:MIME-Version:References: Message-ID:To:Date:Sender:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=UIgcrXRJ7iyQF7TP+uHNEKeKmgJ/rLvK8PfzJGevFlw=; b=iFM47XUBA52XWreIAQbAO9Rp/o sDF0G2Puf0UiR6j8933KMip1EGFuOQh0qsLumNr4Jrr605fLYq97ryZ/wcd0wvEFZmeyZeksoTFMn d9x3JqPf5vHjbZIWjK9DQ3cpRIP1PezntgJZOzN1MLa8J2xZkBjinv/QAyGtv5AsPkhI=; Received: from [127.0.0.1] (helo=sfs-ml-4.v29.lw.sourceforge.com) by sfs-ml-4.v29.lw.sourceforge.com with esmtp (Exim 4.95) (envelope-from ) id 1uZaSD-00061H-6d; Wed, 09 Jul 2025 19:27:41 +0000 Received: from [172.30.29.66] (helo=mx.sourceforge.net) by sfs-ml-4.v29.lw.sourceforge.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from ) id 1uZaSC-00061B-Jm for linux-f2fs-devel@lists.sourceforge.net; Wed, 09 Jul 2025 19:27:40 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sourceforge.net; s=x; h=In-Reply-To:Content-Type:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=iAKyw9SiS7tAPeT8yFNEhG/mFr69U9y6Ca86gIdVh3w=; b=Ee+G8wg9NNqMZU0C3dJILofjiJ b2k5iUMnzPjKRO1vOoaftA59Pxc9OhqSY67pX2ki0olvQmFbeztt8L/2JnrchTa/lAi5gYJAeeoPi 9ri6Ew1Ityu20/k4jwG2xR5NUa3GSo7UKQg/SGyC0dk+s0oPFmunSt8OKKRCv46yqJXI=; DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sf.net; s=x ; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To :From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=iAKyw9SiS7tAPeT8yFNEhG/mFr69U9y6Ca86gIdVh3w=; b=W/ZXcUrkNupH7p0xZHbH65ByN2 2TlMOhWQzjVO4Rbdf1fSkeryZCOUjW96IaGYIEClFTx4vpbv7IsXNadnMVRat/gUGXdONR8OTvGDz eHfR2sYgLw208TXzvzJunUMRJ/VztFsl/m7kyiHpWm+JvKJwDJ9gckClUyRNAJyYq8S8=; Received: from sea.source.kernel.org ([172.234.252.31]) by sfi-mx-2.v28.lw.sourceforge.com with esmtps (TLS1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.95) id 1uZaSC-0005Mu-5E for linux-f2fs-devel@lists.sourceforge.net; Wed, 09 Jul 2025 19:27:40 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by sea.source.kernel.org (Postfix) with ESMTP id C4AB04362E; Wed, 9 Jul 2025 19:27:34 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 61672C4CEEF; Wed, 9 Jul 2025 19:27:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1752089254; bh=Zm+FZCamXFOfYZVRCK0BZ5RTFEHBxsMTaWL62PvvIec=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=tPpKm1tdvE3ARsw+TSv1uypiy1hysiratTvCWm6vUTCuPzCxYQG6Fxd+hiYAaZxTf 10aHeuPAJyFJrwqjOLVTOh+uXYVA9Xka5uOBboT312UEjfa45Lop/Qwh4VNxv2B/6g i2nmJnQkX3guMBfi/dvMWsPpiQ5ac8ORB3lf4OcGGOq5VrY5LwkXdoKOCI1ejRerNK 7q1dhRLxF4MvQmBBB/rBRDvcWjMagYnHI5DewDrgLechb1Axm60uYJ0KEM1BN5pY1Y nlhcbGe+TuqG/3l1hQN5ZLl3/fTnwJImeh7zL9ru3SGV6tVAxddg94N7Qd88KxndEs GgfY895mRO6iQ== Date: Wed, 9 Jul 2025 12:26:50 -0700 To: fsverity@lists.linux.dev Message-ID: <20250709192650.GB28537@sol> References: <20250630172224.46909-1-ebiggers@kernel.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20250630172224.46909-1-ebiggers@kernel.org> X-Headers-End: 1uZaSC-0005Mu-5E Subject: Re: [f2fs-dev] [PATCH 0/2] Convert fs/verity/ to use SHA-2 library API X-BeenThere: linux-f2fs-devel@lists.sourceforge.net X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Eric Biggers via Linux-f2fs-devel Reply-To: Eric Biggers Cc: "Jason A . Donenfeld" , Theodore Ts'o , linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, linux-crypto@vger.kernel.org, linux-ext4@vger.kernel.org, Ard Biesheuvel , linux-btrfs@vger.kernel.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: linux-f2fs-devel-bounces@lists.sourceforge.net On Mon, Jun 30, 2025 at 10:22:22AM -0700, Eric Biggers wrote: > This series, including all its prerequisites, is also available at: > > git fetch https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git fsverity-libcrypto-v1 > > This series makes fs/verity/ use the SHA-2 library API instead of the > old-school crypto API. This is simpler and more efficient. > > This depends on my SHA-2 library improvements for 6.17 (many patches), > so this patchset might need to wait until 6.18. But I'm also thinking > about just basing the fsverity tree on libcrypto-next for 6.17. > > Eric Biggers (2): > lib/crypto: hash_info: Move hash_info.c into lib/crypto/ > fsverity: Switch from crypto_shash to SHA-2 library FYI, I've applied this series to https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git/log/?h=libcrypto-next so that it gets linux-next coverage. As mentioned, it depends on the SHA-256 and SHA-512 improvements in lib/crypto/. But Linus has also expressed a preference to not put too much in one pull request. My current plan is to do 3 pull requests: 1. "Crypto library updates" - most patches, mainly SHA-256 and SHA-512 library improvements 2. "Crypto library tests" - based on (1) but adds: lib/crypto: tests: Add hash-test-template.h and gen-hash-testvecs.py lib/crypto: tests: Add KUnit tests for SHA-224 and SHA-256 lib/crypto: tests: Add KUnit tests for SHA-384 and SHA-512 lib/crypto: tests: Add KUnit tests for Poly1305 3. "Crypto library conversions" - based on (1) but adds: apparmor: use SHA-256 library API instead of crypto_shash API fsverity: Explicitly include fsverity: Switch from crypto_shash to SHA-2 library I'll put all of these in libcrypto-next for linux-next coverage, but (3) will have a slightly different base commit in the final version. - Eric _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel