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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (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 A640DC3DA41 for ; Wed, 10 Jul 2024 18:14:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=Z7U/P+adBShwFG+6BGYRoo0rmiQAMzA8JOjPSNM8dOs=; b=TZd6rWRAEeMOrvq/ESP3x2MjGy huL9iXrkLn+M7n/qSOjDvkNiHf/105xZHJhziQuKCjwhH8fy/f4CleHy2nnC9m/4DbU0XQZjgo6Xx xkG1j36Mr7t0h3l3Dl1XF7uhU2fRxS+FY9/e1WsyV2jNav1dRFjQ45zhYtKf3sfbWJUAWDbBoQ3tF O6nx8X/aA5t5jAuCDtUnzb97djSjzWkeIW6UPL9gdcUh6bD/PA1jdaKLiHOueNUuFzdb1VFr3PHvo gCDGGFI1trFGjBCVewHhpvRxwtcqzcFRoytcjqbPENEU6oFffiZYXzLiM+rUFDjlTgEB876jME6qc t667XaXA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1sRbpt-0000000BOkS-1MH0; Wed, 10 Jul 2024 18:14:37 +0000 Received: from dfw.source.kernel.org ([2604:1380:4641:c500::1]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1sRbpc-0000000BOgA-0Lqd for linux-arm-kernel@lists.infradead.org; Wed, 10 Jul 2024 18:14:21 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by dfw.source.kernel.org (Postfix) with ESMTP id 0E00A61485; Wed, 10 Jul 2024 18:14:19 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 7F361C32781; Wed, 10 Jul 2024 18:14:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1720635258; bh=PqIZtFDhIR4aNKnB7bdK7qEmMFV28vA12grouRhrCnc=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=pXtalsw5iz8YAtDSUtRUcz4U6SUkkNsO4Hf5KtdpaeGDbwgs+RyjdqS6FoxUmsB0K cMvP+ctndr/FXvGNX9oGmuY6nJ6bVrTQ8WnTipRBPmhtvXWxdfNGKkPkNpnC1PBLPX nwmq3tbWxkN+n1ls9p6daaNXmZsaiFo/Z5A6HsmY0doaX9q2Es6eBSM1P0R8jLO9mp WFW+9v/mXfPqnyc5YFPhD2x8rQzr7zdnfZ7jTjTnKiZ8SUy+2UQjcUccLQdG9prqGG kDefCRJns6BEqbA062CRlvdXw0YiQCqPDQKXg3NDDiVTWWKdZ+Rm84+j2XLkcN89YY VDhcHs72ML4/w== Date: Wed, 10 Jul 2024 18:14:17 +0000 From: Eric Biggers To: Mikulas Patocka Cc: linux-crypto@vger.kernel.org, fsverity@lists.linux.dev, dm-devel@lists.linux.dev, x86@kernel.org, linux-arm-kernel@lists.infradead.org, Ard Biesheuvel , Sami Tolvanen , Bart Van Assche , Herbert Xu , Mike Snitzer , Jonathan Brassow Subject: Re: [PATCH v5 00/15] Optimize dm-verity and fsverity using multibuffer hashing Message-ID: <20240710181417.GA58377@google.com> References: <20240611034822.36603-1-ebiggers@kernel.org> <7097bafd-e146-99a5-7f86-369e8e2b080@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7097bafd-e146-99a5-7f86-369e8e2b080@redhat.com> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240710_111420_291157_8311156B X-CRM114-Status: GOOD ( 11.82 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Wed, Jul 10, 2024 at 12:54:24PM +0200, Mikulas Patocka wrote: > Hi > > I'd like to ask what's the status of this patchset. > > Will Herbert accept it? What's the planned kernel version where it will > appear? > > Mikulas It's blocked by Herbert wanting to design the multibuffer hashing API in a more complex way that doesn't make sense. See the previous discussions. I don't know when Herbert will change his mind, so for now I've shifted my focus to the Android kernels. (In the mean time, the improvements that don't depend on the actual multibuffer hashing API still make sense to apply upstream, though.) - Eric