From: Herbert Xu <herbert@gondor.apana.org.au>
To: Tadeusz Struk <tadeusz.struk@intel.com>
Cc: davem@davemloft.net, ahsan.atta@intel.com,
linux-crypto@vger.kernel.org, qat-linux@intel.com
Subject: Re: [PATCH] crypto: qat - fix double release_firmware on error path
Date: Tue, 7 Apr 2015 21:36:47 +0800 [thread overview]
Message-ID: <20150407133647.GC19660@gondor.apana.org.au> (raw)
In-Reply-To: <20150403154117.1172.27874.stgit@tstruk-mobl1>
On Fri, Apr 03, 2015 at 08:41:17AM -0700, Tadeusz Struk wrote:
> release_firmware was called twice on error path causing an Oops.
>
> Reported-by: Ahsan Atta <ahsan.atta@intel.com>
> Signed-off-by: Tadeusz Struk <tadeusz.struk@intel.com>
Applied.
--
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
prev parent reply other threads:[~2015-04-07 13:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-03 15:41 [PATCH] crypto: qat - fix double release_firmware on error path Tadeusz Struk
2015-04-07 13:36 ` Herbert Xu [this message]
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=20150407133647.GC19660@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=ahsan.atta@intel.com \
--cc=davem@davemloft.net \
--cc=linux-crypto@vger.kernel.org \
--cc=qat-linux@intel.com \
--cc=tadeusz.struk@intel.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