Linux cryptographic layer development
 help / color / mirror / Atom feed
From: "Cabiddu, Giovanni" <giovanni.cabiddu@intel.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
	Yosry Ahmed <yosry.ahmed@linux.dev>,
	Kanchana P Sridhar <kanchana.p.sridhar@intel.com>,
	Sergey Senozhatsky <senozhatsky@chromium.org>
Subject: Re: [v3 PATCH 5/8] crypto: acomp - Add request chaining and virtual addresses
Date: Mon, 24 Mar 2025 09:39:53 +0000	[thread overview]
Message-ID: <Z+EoaVTA4xEtECfp@gcabiddu-mobl.ger.corp.intel.com> (raw)
In-Reply-To: <Z9zQALjYg7F_ZXUs@gondor.apana.org.au>

On Fri, Mar 21, 2025 at 10:33:36AM +0800, Herbert Xu wrote:
> On Thu, Mar 20, 2025 at 05:24:57PM +0000, Cabiddu, Giovanni wrote:
> >
> > > +static int acomp_reqchain_finish(struct acomp_req_chain *state,
> > > +				 int err, u32 mask)
> > > +{
> > > +	struct acomp_req *req0 = state->req0;
> > > +	struct acomp_req *req = state->cur;
> > > +	struct acomp_req *n;
> > > +
> > > +	acomp_reqchain_virt(state, err);
> > > +
> > > +	if (req != req0)
> > I'm hitting a NULL pointer dereference at this point as req0 is NULL.
> 
> Yes sorry, my testing was screwed up.  When I thought I was testing
> the chaining fallback path I was actually testing the shash
> fall-through path.
No problem. The set fix that you sent, "Fix synchronous fallback path for
request chaining", resolved the issue.

Thanks,

-- 
Giovanni

  reply	other threads:[~2025-03-24  9:40 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-09  2:43 [v3 PATCH 0/8] crypto: acomp - Add request chaining and virtual address support Herbert Xu
2025-03-09  2:43 ` [v3 PATCH 1/8] crypto: api - Add cra_type->destroy hook Herbert Xu
2025-03-09  2:43 ` [v3 PATCH 2/8] crypto: scomp - Remove tfm argument from alloc/free_ctx Herbert Xu
2025-03-09  2:43 ` [v3 PATCH 3/8] crypto: acomp - Move stream management into scomp layer Herbert Xu
2025-03-16  4:36   ` Eric Biggers
2025-03-16  4:42     ` Herbert Xu
2025-03-16  4:46       ` Herbert Xu
2025-03-16  4:44     ` Herbert Xu
2025-03-17  8:36     ` Herbert Xu
2025-03-09  2:43 ` [v3 PATCH 4/8] crypto: scomp - Disable BH when taking per-cpu spin lock Herbert Xu
2025-03-09  2:43 ` [v3 PATCH 5/8] crypto: acomp - Add request chaining and virtual addresses Herbert Xu
2025-03-16  4:49   ` Eric Biggers
2025-03-16  5:43     ` Herbert Xu
2025-03-16  6:50       ` Eric Biggers
2025-03-20 17:24   ` Cabiddu, Giovanni
2025-03-21  2:33     ` Herbert Xu
2025-03-24  9:39       ` Cabiddu, Giovanni [this message]
2025-03-09  2:43 ` [v3 PATCH 6/8] crypto: testmgr - Remove NULL dst acomp tests Herbert Xu
2025-03-09  2:43 ` [v3 PATCH 7/8] crypto: scomp - Remove support for most non-trivial destination SG lists Herbert Xu
2025-03-10 19:31   ` Dan Carpenter
2025-03-11  3:13     ` Herbert Xu
2025-03-11  3:16       ` Herbert Xu
2025-03-09  2:43 ` [v3 PATCH 8/8] crypto: scomp - Add chaining and virtual address support Herbert Xu

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=Z+EoaVTA4xEtECfp@gcabiddu-mobl.ger.corp.intel.com \
    --to=giovanni.cabiddu@intel.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=kanchana.p.sridhar@intel.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=senozhatsky@chromium.org \
    --cc=yosry.ahmed@linux.dev \
    /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