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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6EF1EC636D3 for ; Wed, 1 Feb 2023 14:38:00 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231911AbjBAOh7 (ORCPT ); Wed, 1 Feb 2023 09:37:59 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43858 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231305AbjBAOhx (ORCPT ); Wed, 1 Feb 2023 09:37:53 -0500 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 04C9169505 for ; Wed, 1 Feb 2023 06:36:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1675262212; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=8/dpDM/3REEz3eyiAc+dJjDInqTxFwwyfLND3C6oXCQ=; b=Agrw8N2cw9QZKQOJXCzcyq4CMFY7eYpl6yk9+s7Sqx2U5OlBfGeWm4zdWfDTi4xKOpfJar EU9Lw2WEjRVMnKf7Xj4kfeYDQGDIjnlUi5AgXYmKeeB7PAFrleQFAOXQY75qLvHZiqHE0l k4e5tKUPVwjg1535uut3l696rcxEfog= Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-292-20SeWIIfNo2jUTyP7mdrOw-1; Wed, 01 Feb 2023 09:36:46 -0500 X-MC-Unique: 20SeWIIfNo2jUTyP7mdrOw-1 Received: from smtp.corp.redhat.com (int-mx09.intmail.prod.int.rdu2.redhat.com [10.11.54.9]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 3223C1C08793; Wed, 1 Feb 2023 14:36:46 +0000 (UTC) Received: from warthog.procyon.org.uk (unknown [10.33.36.97]) by smtp.corp.redhat.com (Postfix) with ESMTP id 44A41492B05; Wed, 1 Feb 2023 14:36:44 +0000 (UTC) Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903 From: David Howells In-Reply-To: References: To: Herbert Xu Cc: dhowells@redhat.com, smfrench@gmail.com, viro@zeniv.linux.org.uk, nspmangalore@gmail.com, rohiths.msft@gmail.com, tom@talpey.com, metze@samba.org, hch@infradead.org, willy@infradead.org, jlayton@kernel.org, linux-cifs@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, sfrench@samba.org, linux-crypto@vger.kernel.org Subject: Re: [PATCH 05/12] cifs: Add a function to Hash the contents of an iterator MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <312907.1675262203.1@warthog.procyon.org.uk> Date: Wed, 01 Feb 2023 14:36:43 +0000 Message-ID: <312908.1675262203@warthog.procyon.org.uk> X-Scanned-By: MIMEDefang 3.1 on 10.11.54.9 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Herbert Xu wrote: > > Add a function to push the contents of a BVEC-, KVEC- or XARRAY-type > > iterator into a symmetric hash algorithm. > > There is no such thing as a symmetric hash. You're using shash > which stands for synchronous hash. Sorry, you're right. > In any case, as I said in the previous review this is abusing the > shash API. Please use ahash instead. It's already abusing the shash API, this doesn't change that, except where it gets the data from. I can have a go at conversion to ahash, but that will have to be a separate patch set as it isn't trivial. The problem is that the current code just assumes it can push bits into the hash as it gets them - this is not possible with ahash. David