From: Lars-Peter Clausen <lars@metafoo.de>
To: Octavian Purdila <octavian.purdila@intel.com>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Josselin Costanzi <josselin.costanzi@mobile-devices.fr>
Subject: Re: [PATCH v5 1/3] iio: add watermark logic to iio read and poll
Date: Wed, 18 Mar 2015 10:37:57 +0100 [thread overview]
Message-ID: <55094775.7010102@metafoo.de> (raw)
In-Reply-To: <CAE1zot+ZJao0zDWNqpjH57oegiVq5E1kGM7dyAepUCd-REUSLQ@mail.gmail.com>
On 03/18/2015 10:29 AM, Octavian Purdila wrote:
> On Wed, Mar 18, 2015 at 11:19 AM, Lars-Peter Clausen <lars@metafoo.de> wrote:
>>> +static ssize_t iio_buffer_store_watermark(struct device *dev,
>>> + struct device_attribute *attr,
>>> + const char *buf,
>>> + size_t len)
>>> +{
>>> + struct iio_dev *indio_dev = dev_to_iio_dev(dev);
>>> + struct iio_buffer *buffer = indio_dev->buffer;
>>> + unsigned int val;
>>> + int ret;
>>> +
>>> + ret = kstrtouint(buf, 10, &val);
>>> + if (ret)
>>> + return ret;
>>> + if (!val)
>>> + return -EINVAL;
>>> +
>>> + mutex_lock(&indio_dev->mlock);
>>> +
>>> + if (val > buffer->length) {
>>> + ret = -EINVAL;
>>> + goto out;
>>> + }
>>
>>
>> This is missing the check for val == 0.
>>
>
> Unless I misunderstand you, the check is done right after kstrtouint()
> before taking the lock.
Yep, sorry overlooked that.
next prev parent reply other threads:[~2015-03-18 9:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 17:56 [PATCH v5 0/3] iio: add support for hardware fifos Octavian Purdila
2015-03-04 17:56 ` [PATCH v5 1/3] iio: add watermark logic to iio read and poll Octavian Purdila
2015-03-14 17:46 ` Jonathan Cameron
2015-03-18 9:19 ` Lars-Peter Clausen
2015-03-18 9:29 ` Octavian Purdila
2015-03-18 9:37 ` Lars-Peter Clausen [this message]
2015-03-19 15:43 ` Octavian Purdila
2015-03-19 15:46 ` Octavian Purdila
2015-03-04 17:56 ` [PATCH v5 2/3] iio: add support for hardware fifo Octavian Purdila
2015-03-14 18:16 ` Jonathan Cameron
2015-03-16 10:05 ` Octavian Purdila
2015-03-21 12:16 ` Jonathan Cameron
2015-03-18 11:55 ` Lars-Peter Clausen
2015-03-18 16:47 ` Octavian Purdila
2015-03-21 12:18 ` Jonathan Cameron
2015-03-04 17:56 ` [PATCH v5 3/3] iio: bmc150_accel: " Octavian Purdila
2015-03-14 18:32 ` Jonathan Cameron
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=55094775.7010102@metafoo.de \
--to=lars@metafoo.de \
--cc=josselin.costanzi@mobile-devices.fr \
--cc=linux-iio@vger.kernel.org \
--cc=octavian.purdila@intel.com \
--cc=srinivas.pandruvada@linux.intel.com \
/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).