From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Kangjie Lu <kjlu@umn.edu>
Cc: pakki001@umn.edu, "Gustavo A. R. Silva" <gustavo@embeddedor.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: drx: fix a missing check of return value
Date: Mon, 7 Jan 2019 17:22:31 -0200 [thread overview]
Message-ID: <20190107172231.49b549db@coco.lan> (raw)
In-Reply-To: <20181220065747.40379-1-kjlu@umn.edu>
Em Thu, 20 Dec 2018 00:57:44 -0600
Kangjie Lu <kjlu@umn.edu> escreveu:
> Function drxj_dap_write_reg16(), which writes data to buffer, may fail.
> We need to check if it fails, and if so, we should goto error.
Did you test this on a real hardware? This kind of patch has a potential
of breaking things, as, on some drivers, some writes may return error.
For example, when called on early stages, a write may fail because
the firmware was not loaded yet. So, a change like that should be
carefully tested with real hardware.
> Otherwise, the buffer will have incorrect data.
>
> Signed-off-by: Kangjie Lu <kjlu@umn.edu>
> ---
> drivers/media/dvb-frontends/drx39xyj/drxj.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/media/dvb-frontends/drx39xyj/drxj.c b/drivers/media/dvb-frontends/drx39xyj/drxj.c
> index 551b7d65fa66..d105125bc1c3 100644
> --- a/drivers/media/dvb-frontends/drx39xyj/drxj.c
> +++ b/drivers/media/dvb-frontends/drx39xyj/drxj.c
> @@ -2136,9 +2136,13 @@ int drxj_dap_atomic_read_write_block(struct i2c_device_addr *dev_addr,
>
> word = ((u16) data[2 * i]);
> word += (((u16) data[(2 * i) + 1]) << 8);
> - drxj_dap_write_reg16(dev_addr,
> + rc = drxj_dap_write_reg16(dev_addr,
> (DRXJ_HI_ATOMIC_BUF_START + i),
> word, 0);
> + if (rc) {
> + pr_err("error %d\n", rc);
> + goto rw_error;
> + }
> }
> }
>
Thanks,
Mauro
prev parent reply other threads:[~2019-01-07 19:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 6:57 [PATCH] media: drx: fix a missing check of return value Kangjie Lu
2019-01-07 19:22 ` Mauro Carvalho Chehab [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=20190107172231.49b549db@coco.lan \
--to=mchehab@kernel.org \
--cc=gustavo@embeddedor.com \
--cc=kjlu@umn.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=pakki001@umn.edu \
/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