From: Eddie James <eajames@linux.vnet.ibm.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
openbmc@lists.ozlabs.org
Cc: Andrew Jeffery <andrew@aj.id.au>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 1/5] fsi/scom: Add mutex around FSI2PIB accesses
Date: Wed, 13 Jun 2018 09:59:01 -0500 [thread overview]
Message-ID: <3f347b72-7be0-11a5-67ec-dc773ed96a46@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180612051911.20690-2-benh@kernel.crashing.org>
On 06/12/2018 12:19 AM, Benjamin Herrenschmidt wrote:
> Otherwise, multiple clients can open the driver and attempt
> to access the PIB at the same time, thus clobbering each other
> in the process.
>
> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Reviewed-by: Eddie James <eajames@linux.vnet.ibm.com>
> ---
> drivers/fsi/fsi-scom.c | 25 ++++++++++++++++++-------
> 1 file changed, 18 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/fsi/fsi-scom.c b/drivers/fsi/fsi-scom.c
> index c8eb5e5b94a7..3cba0eb645e1 100644
> --- a/drivers/fsi/fsi-scom.c
> +++ b/drivers/fsi/fsi-scom.c
> @@ -37,6 +37,7 @@ struct scom_device {
> struct list_head link;
> struct fsi_device *fsi_dev;
> struct miscdevice mdev;
> + struct mutex lock;
> char name[32];
> int idx;
> };
> @@ -53,21 +54,26 @@ static int put_scom(struct scom_device *scom_dev, uint64_t value,
> int rc;
> uint32_t data;
>
> + mutex_lock(&scom_dev->lock);
> +
> data = cpu_to_be32((value >> 32) & 0xffffffff);
> rc = fsi_device_write(scom_dev->fsi_dev, SCOM_DATA0_REG, &data,
> sizeof(uint32_t));
> if (rc)
> - return rc;
> + goto bail;
>
> data = cpu_to_be32(value & 0xffffffff);
> rc = fsi_device_write(scom_dev->fsi_dev, SCOM_DATA1_REG, &data,
> sizeof(uint32_t));
> if (rc)
> - return rc;
> + goto bail;
>
> data = cpu_to_be32(SCOM_WRITE_CMD | addr);
> - return fsi_device_write(scom_dev->fsi_dev, SCOM_CMD_REG, &data,
> + rc = fsi_device_write(scom_dev->fsi_dev, SCOM_CMD_REG, &data,
> sizeof(uint32_t));
> + bail:
> + mutex_unlock(&scom_dev->lock);
> + return rc;
> }
>
> static int get_scom(struct scom_device *scom_dev, uint64_t *value,
> @@ -76,27 +82,31 @@ static int get_scom(struct scom_device *scom_dev, uint64_t *value,
> uint32_t result, data;
> int rc;
>
> +
> + mutex_lock(&scom_dev->lock);
> *value = 0ULL;
> data = cpu_to_be32(addr);
> rc = fsi_device_write(scom_dev->fsi_dev, SCOM_CMD_REG, &data,
> sizeof(uint32_t));
> if (rc)
> - return rc;
> + goto bail;
>
> rc = fsi_device_read(scom_dev->fsi_dev, SCOM_DATA0_REG, &result,
> sizeof(uint32_t));
> if (rc)
> - return rc;
> + goto bail;
>
> *value |= (uint64_t)cpu_to_be32(result) << 32;
> rc = fsi_device_read(scom_dev->fsi_dev, SCOM_DATA1_REG, &result,
> sizeof(uint32_t));
> if (rc)
> - return rc;
> + goto bail;
>
> *value |= cpu_to_be32(result);
>
> - return 0;
> + bail:
> + mutex_unlock(&scom_dev->lock);
> + return rc;
> }
>
> static ssize_t scom_read(struct file *filep, char __user *buf, size_t len,
> @@ -183,6 +193,7 @@ static int scom_probe(struct device *dev)
> if (!scom)
> return -ENOMEM;
>
> + mutex_init(&scom->lock);
> scom->idx = ida_simple_get(&scom_ida, 1, INT_MAX, GFP_KERNEL);
> snprintf(scom->name, sizeof(scom->name), "scom%d", scom->idx);
> scom->fsi_dev = fsi_dev;
next prev parent reply other threads:[~2018-06-13 14:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 5:19 [RFC PATCH 0/5] FSI scom driver overhaul Benjamin Herrenschmidt
2018-06-12 5:19 ` [RFC PATCH 1/5] fsi/scom: Add mutex around FSI2PIB accesses Benjamin Herrenschmidt
2018-06-13 14:59 ` Eddie James [this message]
2018-06-12 5:19 ` [RFC PATCH 2/5] fsi/scom: Whitespace fixes Benjamin Herrenschmidt
2018-06-13 14:58 ` Eddie James
2018-06-12 5:19 ` [RFC PATCH 3/5] fsi/scom: Fixup endian annotations Benjamin Herrenschmidt
2018-06-13 14:58 ` Eddie James
2018-06-12 5:19 ` [RFC PATCH 4/5] fsi/scom: Add register definitions Benjamin Herrenschmidt
2018-06-13 14:57 ` Eddie James
2018-06-12 5:19 ` [RFC PATCH 5/5] fsi/scom: Major overhaul Benjamin Herrenschmidt
2018-06-13 14:57 ` Eddie James
2018-06-13 23:00 ` Benjamin Herrenschmidt
2018-06-14 14:12 ` Eddie James
2018-06-16 5:04 ` Joel Stanley
2018-06-17 1:17 ` Benjamin Herrenschmidt
2018-06-17 1:22 ` Benjamin Herrenschmidt
2018-06-18 4:09 ` Alistair Popple
2018-06-18 4:46 ` Benjamin Herrenschmidt
2018-06-18 5:05 ` Alistair Popple
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=3f347b72-7be0-11a5-67ec-dc773ed96a46@linux.vnet.ibm.com \
--to=eajames@linux.vnet.ibm.com \
--cc=andrew@aj.id.au \
--cc=benh@kernel.crashing.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.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®