Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Vladislav Dronov <vdronov@redhat.com>
To: herbert@gondor.apana.org.au
Cc: akhilrajeev@nvidia.com, linux-crypto@vger.kernel.org,
	ptalbert@redhat.com, vdronov@redhat.com
Subject: Re: [PATCH] crypto: tegra - Fix dma_free_coherent size error
Date: Tue, 19 May 2026 14:24:05 +0200	[thread overview]
Message-ID: <20260519122405.10860-1-vdronov@redhat.com> (raw)
In-Reply-To: <agvleqNqloWB6tpf@gondor.apana.org.au>

On Tue, May 19, 2026 at 6:22 AM Herbert Xu <herbert@gondor.apana.org.au> wrote:
>
>         /* Allocate buffers required */
> -       rctx->inbuf.size = rctx->assoclen + rctx->authsize + rctx->cryptlen + 100;
> -       rctx->inbuf.buf = dma_alloc_coherent(ctx->se->dev, rctx->inbuf.size,
> +       bufsize = rctx->assoclen + rctx->authsize + rctx->cryptlen + 100;
> +       rctx->inbuf.size = bufsize;
> +       rctx->inbuf.buf = dma_alloc_coherent(ctx->se->dev, bufsize,
>                                              &rctx->inbuf.addr, GFP_KERNEL);
>         if (!rctx->inbuf.buf)
>                 goto out_finalize;

sashiko.dev makes a point here ( https://sashiko.dev/#/patchset/agvleqNqloWB6tpf%40gondor.apana.org.au )
that the code does not set ret to an error value, as done in the other similar places, see:

> -       rctx->outbuf.size = rctx->assoclen + rctx->authsize + rctx->cryptlen + 100;
> -       rctx->outbuf.buf = dma_alloc_coherent(ctx->se->dev, rctx->outbuf.size,
> +       rctx->outbuf.size = bufsize;
> +       rctx->outbuf.buf = dma_alloc_coherent(ctx->se->dev, bufsize,
>                                               &rctx->outbuf.addr, GFP_KERNEL);
>         if (!rctx->outbuf.buf) {
>                 ret = -ENOMEM;                    <<< HERE
                  goto out_free_inbuf;
          }

This looks valid to me, I'd suggest to add {}s and:

+                 ret = -ENOMEM;

to the patch indeed.

Best regards,
Vladislav Dronov


  reply	other threads:[~2026-05-19 12:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-19  4:22 [PATCH] crypto: tegra - Fix dma_free_coherent size error Herbert Xu
2026-05-19 12:24 ` Vladislav Dronov [this message]
     [not found] ` <CAMusb+T_q1Vu3MD+VjiPWfpe3NNpjJehXWQ9gePo=hM+NGm1zg@mail.gmail.com>
2026-05-20  2:51   ` [PATCH] crypto: tegra - Return ENOMEM when input buffer allocation fails for ccm Herbert Xu
2026-05-20 16:08     ` Vladislav Dronov
2026-05-20 16:28     ` Vladislav Dronov
2026-05-20 16:03 ` [PATCH] crypto: tegra - Fix dma_free_coherent size error Vladislav Dronov

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=20260519122405.10860-1-vdronov@redhat.com \
    --to=vdronov@redhat.com \
    --cc=akhilrajeev@nvidia.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=ptalbert@redhat.com \
    /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