From: Herbert Xu <herbert@gondor.apana.org.au>
To: Brad Bosch <bradbosch@comcast.net>
Cc: linux-crypto@vger.kernel.org, netdev@vger.kernel.org, offbase0@gmail.com
Subject: Re: Crypto oops in async_chainiv_do_postponed
Date: Tue, 1 Sep 2009 08:04:59 +1000 [thread overview]
Message-ID: <20090831220459.GA15713@gondor.apana.org.au> (raw)
In-Reply-To: <19099.63038.425414.514063@waldo.imnotcreative.homeip.net>
On Mon, Aug 31, 2009 at 11:11:42AM -0500, Brad Bosch wrote:
>
> OK. I was looking for something subtle because the crash takes a long
> time to happen. But do you agree that the race I described above also
> a real bug?
No I don't think it is. CHAINV_STATE_INUSE guarantees that only
one entity can use ctx->err at any time.
> Yes, I see that this bug must be the bug we would likely encounter first.
> Apparently, async_chainiv_do_postponed was never tested? But I don't
> see how the patch you proposed below helps. We still don't seem to be
> returning NULL from skcipher_dequeue_givcrypt when we reach the end of
> the queue because __crypto_dequeue_request is not checking for NULL
> before it subtracts offset.
Where we subtract the offset the pointer can never be NULL. Please
try my patch.
Thanks,
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2009-08-31 22:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <19095.1264.682820.125602@waldo.imnotcreative.homeip.net>
2009-08-29 10:46 ` Crypto oops in async_chainiv_do_postponed Herbert Xu
2009-08-31 16:11 ` Brad Bosch
2009-08-31 22:04 ` Herbert Xu [this message]
2009-09-01 15:42 ` Brad Bosch
2009-09-01 22:17 ` Herbert Xu
2009-09-02 14:08 ` Brad Bosch
2009-09-02 21:57 ` Herbert Xu
2009-09-02 23:47 ` Brad Bosch
2009-09-03 1:53 ` Herbert Xu
2009-09-02 14:23 ` Brad Bosch
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=20090831220459.GA15713@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=bradbosch@comcast.net \
--cc=linux-crypto@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=offbase0@gmail.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