From: "Colin King (gmail)" <colin.i.king@gmail.com>
To: "David E. Box" <david.e.box@linux.intel.com>
Cc: Mark Gross <markgross@kernel.org>,
Hans de Goede <hdegoede@redhat.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
platform-driver-x86@vger.kernel.org
Subject: re: platform/x86: Add Intel Software Defined Silicon driver
Date: Thu, 24 Feb 2022 22:25:51 +0000 [thread overview]
Message-ID: <13f987a0-197a-d0db-6f97-c7358d4723da@gmail.com> (raw)
Hi,
Static analysis with clang scan has detected a potential issue in the
following commit:
commit 2546c60004309ede8e2d1d5341e0decd90e057bf
Author: David E. Box <david.e.box@linux.intel.com>
Date: Fri Feb 11 17:32:50 2022 -0800
platform/x86: Add Intel Software Defined Silicon driver
The issue is as follows:
static int sdsi_mbox_read(struct sdsi_priv *priv, struct sdsi_mbox_info
*info, size_t *data_size)
{
int ret;
lockdep_assert_held(&priv->mb_lock);
ret = sdsi_mbox_acquire(priv, info);
if (ret)
return ret;
Note: the return above does not assign a value to *data_size
return sdsi_mbox_cmd_read(priv, info, data_size);
}
static long state_certificate_read(struct file *filp, struct kobject *kobj,
struct bin_attribute *attr, char
*buf, loff_t off,
size_t count)
{
struct device *dev = kobj_to_dev(kobj);
struct sdsi_priv *priv = dev_get_drvdata(dev);
u64 command = SDSI_CMD_READ_STATE;
struct sdsi_mbox_info info;
size_t size;
^
Note: size is not initialized
int ret;
if (!priv->sdsi_enabled)
return -EPERM;
if (off)
return 0;
/* Buffer for return data */
info.buffer = kmalloc(SDSI_SIZE_READ_MSG, GFP_KERNEL);
if (!info.buffer)
return -ENOMEM;
info.payload = &command;
info.size = sizeof(command);
ret = mutex_lock_interruptible(&priv->mb_lock);
if (ret)
goto free_buffer;
ret = sdsi_mbox_read(priv, &info, &size);
Note: a failure in scsi_mbox_read can lead to variable size not being
assigned a value.
mutex_unlock(&priv->mb_lock);
if (ret < 0)
goto free_buffer;
Note: failure with ret < 0 going to free_buffer
if (size > count)
size = count;
memcpy(buf, info.buffer, size);
free_buffer:
kfree(info.buffer);
if (ret)
return ret;
return size;
Note: uninitialized value in size being returned. This is an error.
}
next reply other threads:[~2022-02-24 22:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 22:25 Colin King (gmail) [this message]
2022-02-25 9:00 ` Hans de Goede
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=13f987a0-197a-d0db-6f97-c7358d4723da@gmail.com \
--to=colin.i.king@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=david.e.box@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=platform-driver-x86@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
all inboxes | Powered by JetHome®