From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org, joshua.a.hay@intel.com,
steffen.klassert@secunet.com
Subject: Re: Git bisected regression for ipsec/aead
Date: Thu, 25 Aug 2016 11:45:19 -0400 [thread overview]
Message-ID: <20160825154519.GD10892@oracle.com> (raw)
In-Reply-To: <20160825084951.GA11496@gondor.apana.org.au>
On (08/25/16 16:49), Herbert Xu wrote:
> This bisection doesn't make much sense as this patch just causes
> cryptd to be used a little more more frequently. But it does
> point the finger at cryptd.
:
> So we have list corruption here, possibly caused by use-after-free.
> I did spot one bug in the AEAD cryptd path where we end up using
> the wrong tfm to track refcnt.
>
> Does this patch help?
Unfortunately no, I still see the panic.
--Sowmini
next prev parent reply other threads:[~2016-08-25 15:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-19 19:21 Git bisected regression for ipsec/aead Sowmini Varadhan
2016-08-25 8:49 ` Herbert Xu
2016-08-25 15:45 ` Sowmini Varadhan [this message]
2016-08-27 10:13 ` Sowmini Varadhan
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=20160825154519.GD10892@oracle.com \
--to=sowmini.varadhan@oracle.com \
--cc=herbert@gondor.apana.org.au \
--cc=joshua.a.hay@intel.com \
--cc=linux-crypto@vger.kernel.org \
--cc=steffen.klassert@secunet.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;
as well as URLs for NNTP newsgroup(s).