public inbox for linux-crypto@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Subject: Re: [v2 PATCH 2/3] crypto: scatterwalk - Add memcpy_sglist
Date: Mon, 10 Mar 2025 10:06:46 -0700	[thread overview]
Message-ID: <20250310170646.GC1701@sol.localdomain> (raw)
In-Reply-To: <Z8whc1HklIA3rBNi@gondor.apana.org.au>

On Sat, Mar 08, 2025 at 06:52:35PM +0800, Herbert Xu wrote:
> On Fri, Mar 07, 2025 at 01:37:49PM -0800, Eric Biggers wrote:
> >
> > There's no user of this yet, but presumably this is going to be used to replace
> > some of the bizarre code that is using the "null skcipher" to copy between two
> > scatterlists?  For example the code in crypto/seqiv.c.
> 
> It was actually for zram:
> 
> https://lore.kernel.org/all/Z8kiRym1hS9fB2mE@gondor.apana.org.au/
> 
> But yes we could definitely replace the null skcipher with this.
> Do you want to have a go at that?
> 

Yes, I'll do that.

- Eric

  reply	other threads:[~2025-03-10 17:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-07  3:36 [v2 PATCH 0/3] crypto: scatterwalk - scatterwalk_next and memcpy_sglist Herbert Xu
2025-03-07  3:36 ` [v2 PATCH 1/3] crypto: scatterwalk - Change scatterwalk_next calling convention Herbert Xu
2025-03-07 21:43   ` Eric Biggers
2025-03-08 10:46     ` Herbert Xu
2025-03-07  3:36 ` [v2 PATCH 2/3] crypto: scatterwalk - Add memcpy_sglist Herbert Xu
2025-03-07 21:37   ` Eric Biggers
2025-03-08 10:52     ` Herbert Xu
2025-03-10 17:06       ` Eric Biggers [this message]
2025-03-11  4:36   ` Eric Biggers
2025-04-26  6:16     ` Herbert Xu
2025-03-07  3:36 ` [v2 PATCH 3/3] crypto: skcipher - Eliminate duplicate virt.addr field Herbert Xu
2025-03-07 21:48   ` Eric Biggers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250310170646.GC1701@sol.localdomain \
    --to=ebiggers@kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox