From: Dan Carpenter <dan.carpenter@oracle.com>
To: sean@mess.org
Cc: linux-media@vger.kernel.org
Subject: re: [media] redrat3: remove memcpys and fix unaligned memory access
Date: Tue, 9 Apr 2013 12:02:59 +0300 [thread overview]
Message-ID: <20130409090259.GA1544@longonot.mountain> (raw)
Hi Sean,
I had a question about 4c055a5ae94c: "[media] redrat3: remove memcpys
and fix unaligned memory access" from Feb 16, 2013.
drivers/media/rc/redrat3.c
619 /* grab the Length and type of transfer */
620 pktlen = be16_to_cpu(header->length);
621 pkttype = be16_to_cpu(header->transfer_type);
622
623 if (pktlen > sizeof(rr3->irdata)) {
624 dev_warn(rr3->dev, "packet length %u too large\n", pktlen);
625 return;
626 }
627
628 switch (pkttype) {
629 case RR3_ERROR:
630 if (len >= sizeof(struct redrat3_error)) {
631 struct redrat3_error *error = rr3->bulk_in_buf;
632 unsigned fw_error = be16_to_cpu(error->fw_error);
633 redrat3_dump_fw_error(rr3, fw_error);
634 }
635 break;
636
637 case RR3_MOD_SIGNAL_IN:
638 memcpy(&rr3->irdata, rr3->bulk_in_buf, len);
^^^
639 rr3->bytes_read = len;
^^^
640 rr3_dbg(rr3->dev, "bytes_read %d, pktlen %d\n",
641 rr3->bytes_read, pktlen);
^^^^^^
Should we be copying "pktlen" bytes on the line before? It seems
inconsistent that it doesn't match the debug code.
My main concern is that we limit the size of "pktlen" but then we only
use it for debug output.
642 break;
regards,
dan carpenter
next reply other threads:[~2013-04-09 9:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 9:02 Dan Carpenter [this message]
2013-04-10 11:42 ` [media] redrat3: remove memcpys and fix unaligned memory access Sean Young
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=20130409090259.GA1544@longonot.mountain \
--to=dan.carpenter@oracle.com \
--cc=linux-media@vger.kernel.org \
--cc=sean@mess.org \
/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