From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] MAX1111: Fix race condition causing NULL pointer exception
Date: Fri, 20 May 2011 22:20:05 +0100 [thread overview]
Message-ID: <20110520212005.GA30675@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <201105200013.20380.morpheus.ibis@gmail.com>
On Fri, May 20, 2011 at 12:13:20AM +0200, Pavel Herrmann wrote:
> From bd55d6b18fa4fcb884980825b43b43df01767149 Mon Sep 17 00:00:00 2001
> From: Pavel Herrmann <morpheus.ibis@gmail.com>
> Date: Mon, 16 May 2011 14:18:18 +0200
> Subject: [PATCH] MAX1111: Fix Race condition causing NULL pointer exception
>
> spi_sync call uses its spi_message parameter to keep completion information,
> having this structure static is not thread-safe, potentially causing one
> thread having pointers to memory on or above other threads stack. use mutex
> to prevent multiple access
>
> Signed-off-by: Pavel Herrmann <morpheus.ibis@gmail.com>
Looks good, thanks.
Acked-by: Russell King <rmk+kernel@arm.linux.org.uk>
> ---
> drivers/hwmon/max1111.c | 12 ++++++++++++
> 1 files changed, 12 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/hwmon/max1111.c b/drivers/hwmon/max1111.c
> index 12a54aa..d872f57 100644
> --- a/drivers/hwmon/max1111.c
> +++ b/drivers/hwmon/max1111.c
> @@ -40,6 +40,7 @@ struct max1111_data {
> struct spi_transfer xfer[2];
> uint8_t *tx_buf;
> uint8_t *rx_buf;
> + struct mutex msg_lock_mutex;
> };
>
> static int max1111_read(struct device *dev, int channel)
> @@ -48,6 +49,11 @@ static int max1111_read(struct device *dev, int channel)
> uint8_t v1, v2;
> int err;
>
> + /* spi_sync requires data not to be freed before function returns
> + * for static data, any access is dangerous, use locks
> + */
> + mutex_lock(&data->msg_lock_mutex);
> +
> data->tx_buf[0] = (channel << MAX1111_CTRL_SEL_SH) |
> MAX1111_CTRL_PD0 | MAX1111_CTRL_PD1 |
> MAX1111_CTRL_SGL | MAX1111_CTRL_UNI | MAX1111_CTRL_STR;
> @@ -55,12 +61,15 @@ static int max1111_read(struct device *dev, int channel)
> err = spi_sync(data->spi, &data->msg);
> if (err < 0) {
> dev_err(dev, "spi_sync failed with %d\n", err);
> + mutex_unlock(&data->msg_lock_mutex);
> return err;
> }
>
> v1 = data->rx_buf[0];
> v2 = data->rx_buf[1];
>
> + mutex_unlock(&data->msg_lock_mutex);
> +
> if ((v1 & 0xc0) || (v2 & 0x3f))
> return -EINVAL;
>
> @@ -176,6 +185,8 @@ static int __devinit max1111_probe(struct spi_device *spi)
> if (err)
> goto err_free_data;
>
> + mutex_init(&data->msg_lock_mutex);
> +
> data->spi = spi;
> spi_set_drvdata(spi, data);
>
> @@ -213,6 +224,7 @@ static int __devexit max1111_remove(struct spi_device
> *spi)
>
> hwmon_device_unregister(data->hwmon_dev);
> sysfs_remove_group(&spi->dev.kobj, &max1111_attr_group);
> + mutex_destroy(data->msg_lock_mutex);
> kfree(data->rx_buf);
> kfree(data->tx_buf);
> kfree(data);
> --
> 1.7.5.rc3
>
next prev parent reply other threads:[~2011-05-20 21:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 15:18 [PATCH] MAX1111: Fix race condition causing NULL pointer exception Pavel Herrmann
2011-05-18 15:29 ` Eric Miao
2011-05-18 15:29 ` Russell King - ARM Linux
2011-05-18 17:36 ` Marek Vasut
2011-05-18 22:47 ` Russell King - ARM Linux
2011-05-19 12:35 ` Pavel Machek
2011-05-19 12:51 ` Pavel Herrmann
2011-05-19 13:55 ` Marek Vasut
2011-05-19 19:31 ` Russell King - ARM Linux
2011-05-19 22:13 ` Pavel Herrmann
2011-05-20 21:20 ` Russell King - ARM Linux [this message]
2011-05-21 20:28 ` Pavel Machek
2011-05-21 20:45 ` Pavel Herrmann
2011-05-22 15:52 ` Marek Vasut
2011-05-18 21:47 ` Cyril Hrubis
2011-06-30 12:36 ` Marek Vasut
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=20110520212005.GA30675@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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).