From: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: Peter Huewe <peterhuewe@gmx.de>,
linux-security-module@vger.kernel.org, stable@vger.kernel.org,
Marcel Selhorst <tpmdd@selhorst.net>,
"moderated list:TPM DEVICE DRIVER"
<tpmdd-devel@lists.sourceforge.net>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tpm_crb: fix mapping of the buffers
Date: Tue, 19 Apr 2016 11:09:53 -0600 [thread overview]
Message-ID: <20160419170953.GB20844@obsidianresearch.com> (raw)
In-Reply-To: <1461059658-8884-1-git-send-email-jarkko.sakkinen@linux.intel.com>
On Tue, Apr 19, 2016 at 12:54:18PM +0300, Jarkko Sakkinen wrote:
> Cc: stable@vger.kernel.org
> Fixes: 1bd047be37d9 ("tpm_crb: Use devm_ioremap_resource")
> Signed-off-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
> drivers/char/tpm/tpm_crb.c | 39 ++++++++++++++++++++++++++++-----------
> 1 file changed, 28 insertions(+), 11 deletions(-)
This looks OK
Reviewed-by: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
> + if (cmd_pa != rsp_pa) {
> + priv->rsp = crb_map_res(dev, priv, &io_res, rsp_pa, rsp_size);
> + return PTR_ERR_OR_ZERO(priv->rsp);
> + }
I would use an else here, 'exit on success' is considered an
anti-pattern.
Eg:
if (cmd_pa == rsp_pa) {
/* According to the PTP specification, overlapping command and response
* buffer sizes must be identical.
*/
if (cmd_size != rsp_size) {
dev_err(dev, FW_BUG "overlapping command and response buffer sizes are not identical");
return -EINVAL;
}
priv->rsp = priv->cmd;
}
else {
priv->rsp = crb_map_res(dev, priv, &io_res, rsp_pa, rsp_size);
if (IS_ERR(priv->rsp))
return PTR_ERR(priv->rsp);
}
return 0;
Jason
next prev parent reply other threads:[~2016-04-19 17:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 9:54 [PATCH] tpm_crb: fix mapping of the buffers Jarkko Sakkinen
2016-04-19 10:00 ` Jarkko Sakkinen
2016-04-19 17:09 ` Jason Gunthorpe [this message]
2016-04-19 18:47 ` Jarkko Sakkinen
-- strict thread matches above, loose matches on Subject: below --
2016-08-19 23:10 Jarkko Sakkinen
2016-09-05 13:58 ` Greg KH
2016-04-18 23:08 Jarkko Sakkinen
2016-04-18 23:34 ` Jason Gunthorpe
2016-04-19 4:59 ` Jarkko Sakkinen
2016-04-19 5:58 ` Jarkko Sakkinen
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=20160419170953.GB20844@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=stable@vger.kernel.org \
--cc=tpmdd-devel@lists.sourceforge.net \
--cc=tpmdd@selhorst.net \
/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).