From: Dan Carpenter <dan.carpenter@oracle.com>
To: kernel-janitors@vger.kernel.org
Subject: re: mailbox: Add generic mechanism for testing Mailbox Controllers
Date: Wed, 21 Oct 2015 20:26:10 +0000 [thread overview]
Message-ID: <20151021202610.GA31470@mwanda> (raw)
Hello Lee Jones,
The patch 8ea4484d0c2b: "mailbox: Add generic mechanism for testing
Mailbox Controllers" from Oct 16, 2015, leads to the following static
checker warning:
drivers/mailbox/mailbox-test.c:71 mbox_test_signal_write()
warn: copy_to/from_user() returns a positive value
drivers/mailbox/mailbox-test.c
42 static ssize_t mbox_test_signal_write(struct file *filp,
43 const char __user *userbuf,
44 size_t count, loff_t *ppos)
45 {
46 struct mbox_test_device *tdev = filp->private_data;
47 int ret;
48
49 if (!tdev->tx_channel) {
50 dev_err(tdev->dev, "Channel cannot do Tx\n");
51 return -EINVAL;
52 }
53
54 if (count > MBOX_MAX_SIG_LEN) {
55 dev_err(tdev->dev,
56 "Signal length %zd greater than max allowed %d\n",
57 count, MBOX_MAX_SIG_LEN);
58 return -EINVAL;
59 }
60
61 tdev->signal = kzalloc(MBOX_MAX_SIG_LEN, GFP_KERNEL);
62 if (!tdev->signal)
63 return -ENOMEM;
This feels racy. Also if ->signal has already been allocated then this
leaks.
64
65 ret = copy_from_user(tdev->signal, userbuf, count);
66 if (ret) {
67 kfree(tdev->signal);
68 return -EFAULT;
69 }
Normally we do it like this:
if (copy_from_user(tdev->signal, userbuf, count)) {
kfree(tdev->signal);
tdev->signal; <-- also let's set it to NULL or it leads
to a use after free.
return -EFAULT;
}
70
71 return ret < 0 ? ret : count;
"ret" is always zero here. But we can just get rid of that variable
completely.
72 }
regards,
dan carpenter
next reply other threads:[~2015-10-21 20:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-21 20:26 Dan Carpenter [this message]
2015-10-26 9:52 ` mailbox: Add generic mechanism for testing Mailbox Controllers Lee Jones
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=20151021202610.GA31470@mwanda \
--to=dan.carpenter@oracle.com \
--cc=kernel-janitors@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).