From: Herbert Xu <herbert@gondor.apana.org.au>
To: Tong Zhang <ztong0001@gmail.com>
Cc: Giovanni Cabiddu <giovanni.cabiddu@intel.com>,
"David S. Miller" <davem@davemloft.net>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Wojciech Ziemba <wojciech.ziemba@intel.com>,
Tadeusz Struk <tadeusz.struk@intel.com>,
qat-linux@intel.com, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 0/2] crypto: qat - fix couple crashes duing error handling
Date: Fri, 26 Mar 2021 20:31:59 +1100 [thread overview]
Message-ID: <20210326093159.GI12658@gondor.apana.org.au> (raw)
In-Reply-To: <20210319034001.435117-1-ztong0001@gmail.com>
On Thu, Mar 18, 2021 at 11:39:58PM -0400, Tong Zhang wrote:
> There are a couple of issues in qat error handling. Those drivers tries to
> release resources that is not initialized. This patch series tries to fix
> crashes caused by incorrect error handling.
>
> v2: removed excessive dump in commit log as suggested by Andy Shevchenko <andy.shevchenko@gmail.com>
> v3: collect tags as suggested by Andy Shevchenko <andy.shevchenko@gmail.com>
> v4: fix commit log typos
> v5: fix headline
>
> Tong Zhang (2):
> crypto: qat - don't release uninitialized resources
> crypto: qat - ADF_STATUS_PF_RUNNING should be set after adf_dev_init
>
> drivers/crypto/qat/qat_c3xxxvf/adf_drv.c | 4 ++--
> drivers/crypto/qat/qat_c62xvf/adf_drv.c | 4 ++--
> drivers/crypto/qat/qat_common/adf_vf_isr.c | 17 +++++++++++++----
> drivers/crypto/qat/qat_dh895xccvf/adf_drv.c | 4 ++--
> 4 files changed, 19 insertions(+), 10 deletions(-)
All applied. Thanks.
--
Email: Herbert Xu <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:[~2021-03-26 9:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 16:22 [PATCH v3 0/2] crypto: qat: fix couple crashes duing error handling Tong Zhang
2021-03-12 16:22 ` [PATCH v3 1/2] crypto: qat - dont release uninitialized resources Tong Zhang
2021-03-18 15:53 ` Giovanni Cabiddu
2021-03-18 16:06 ` Giovanni Cabiddu
2021-03-18 16:21 ` [PATCH v4 0/2] crypto: qat: fix couple crashes duing error handling Tong Zhang
2021-03-18 16:21 ` [PATCH v4 1/2] crypto: qat - don't release uninitialized resources Tong Zhang
2021-03-18 16:21 ` [PATCH v4 2/2] crypto: qat: ADF_STATUS_PF_RUNNING should be set after adf_dev_init Tong Zhang
2021-03-18 17:17 ` Giovanni Cabiddu
2021-03-19 3:39 ` [PATCH v5 0/2] crypto: qat - fix couple crashes duing error handling Tong Zhang
2021-03-19 3:39 ` [PATCH v5 1/2] crypto: qat - don't release uninitialized resources Tong Zhang
2021-03-19 3:40 ` [PATCH v5 2/2] crypto: qat - ADF_STATUS_PF_RUNNING should be set after adf_dev_init Tong Zhang
2021-03-26 9:31 ` Herbert Xu [this message]
2021-03-19 3:41 ` [PATCH v4 2/2] crypto: qat: " Tong Zhang
2021-03-18 16:22 ` [PATCH v3 1/2] crypto: qat - dont release uninitialized resources Tong Zhang
2021-03-12 16:22 ` [PATCH v3 2/2] crypto: qat: ADF_STATUS_PF_RUNNING should be set after adf_dev_init Tong Zhang
2021-03-18 16:03 ` Giovanni Cabiddu
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=20210326093159.GI12658@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=andy.shevchenko@gmail.com \
--cc=davem@davemloft.net \
--cc=giovanni.cabiddu@intel.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qat-linux@intel.com \
--cc=tadeusz.struk@intel.com \
--cc=wojciech.ziemba@intel.com \
--cc=ztong0001@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.