Linux Media Controller development
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: sean@mess.org
Cc: linux-media@vger.kernel.org
Subject: [bug report] media: lirc: improve locking
Date: Wed, 13 Dec 2017 13:07:31 +0300	[thread overview]
Message-ID: <20171213100731.2oamrvxqdfkhml4d@mwanda> (raw)

Hello Sean Young,

The patch 131fd7fc3c01: "media: lirc: improve locking" from Nov 4,
2017, leads to the following static checker warning:

	drivers/media/rc/lirc_dev.c:373 ir_lirc_transmit_ir()
	error: 'txbuf' dereferencing possible ERR_PTR()

drivers/media/rc/lirc_dev.c
   330                  txbuf = memdup_user(buf, n);
   331                  if (IS_ERR(txbuf)) {
   332                          ret = PTR_ERR(txbuf);
   333                          goto out;
                                ^^^^^^^^
This used to be a direct return...

   334                  }
   335          }
   336  
   337          for (i = 0; i < count; i++) {
   338                  if (txbuf[i] > IR_MAX_DURATION / 1000 - duration || !txbuf[i]) {
   339                          ret = -EINVAL;
   340                          goto out;
   341                  }
   342  
   343                  duration += txbuf[i];
   344          }
   345  
   346          ret = dev->tx_ir(dev, txbuf, count);
   347          if (ret < 0)
   348                  goto out;
   349  
   350          if (fh->send_mode == LIRC_MODE_SCANCODE) {
   351                  ret = n;
   352          } else {
   353                  for (duration = i = 0; i < ret; i++)
   354                          duration += txbuf[i];
   355  
   356                  ret *= sizeof(unsigned int);
   357  
   358                  /*
   359                   * The lircd gap calculation expects the write function to
   360                   * wait for the actual IR signal to be transmitted before
   361                   * returning.
   362                   */
   363                  towait = ktime_us_delta(ktime_add_us(start, duration),
   364                                          ktime_get());
   365                  if (towait > 0) {
   366                          set_current_state(TASK_INTERRUPTIBLE);
   367                          schedule_timeout(usecs_to_jiffies(towait));
                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This looks like a long wait?  Are you sure you want to hold the lock
this whole time?

   368                  }
   369          }
   370  
   371  out:
   372          mutex_unlock(&dev->lock);
   373          kfree(txbuf);
                      ^^^^^
Can't pass an error pointer to kfree().

   374          kfree(raw);

regards,
dan carpenter

             reply	other threads:[~2017-12-13 10:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-13 10:07 Dan Carpenter [this message]
2017-12-13 13:57 ` [bug report] media: lirc: improve locking 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=20171213100731.2oamrvxqdfkhml4d@mwanda \
    --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