From: Jonathan Cameron <jic23@cam.ac.uk>
To: Sasha Levin <levinsasha928@gmail.com>, linux-kernel@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
linux-iio@vger.kernel.org, devel@driverdev.osuosl.org
Subject: Re: [PATCH] iio: Fix build error in industrialio-core.c
Date: Thu, 24 Nov 2011 08:49:51 +0000 [thread overview]
Message-ID: <4e3c37a6-3777-4138-800b-f055f7caa8f3@email.android.com> (raw)
In-Reply-To: <1322043239-26082-1-git-send-email-levinsasha928@gmail.com>
Sasha Levin <levinsasha928@gmail.com> wrote:
>The error was introduced in commit b4641336 ("iio: fix a leak due to
>improper use of anon_inode_getfd()").
>
>Looks like the code wasn't even compile tested. Instead of just fixing
>the
>error I changed the function a bit to make it nicer.
Minimal change would have been slightly nicer but clean up is obvious so fine. Thanks for doing this. Andrew m has a dirty build fix in NM but he will drop that when this hits.
>Cc: Jonathan Cameron <jic23@cam.ac.uk>
>Cc: Greg Kroah-Hartman <gregkh@suse.de>
>Cc: linux-iio@vger.kernel.org
>Cc: devel@driverdev.osuosl.org
>Signed-off-by: Sasha Levin <levinsasha928@gmail.com>
Acked-by: Jonathan Cameron <jic23@kernel.org>
>---
> drivers/staging/iio/industrialio-core.c | 21 ++++++++++-----------
> 1 files changed, 10 insertions(+), 11 deletions(-)
>
>diff --git a/drivers/staging/iio/industrialio-core.c
>b/drivers/staging/iio/industrialio-core.c
>index 2656409..5367914 100644
>--- a/drivers/staging/iio/industrialio-core.c
>+++ b/drivers/staging/iio/industrialio-core.c
>@@ -242,25 +242,24 @@ static const struct file_operations
>iio_event_chrdev_fileops = {
>
> static int iio_event_getfd(struct iio_dev *indio_dev)
> {
>+ struct iio_event_interface *ev_int = indio_dev->event_interface;
> int fd;
>
>- if (indio_dev->event_interface == NULL)
>+ if (ev_int == NULL)
> return -ENODEV;
>
>- mutex_lock(&indio_dev->event_interface->event_list_lock);
>- if (test_and_set_bit(IIO_BUSY_BIT_POS,
>- &indio_dev->event_interface->flags)) {
>- mutex_unlock(&indio_dev->event_interface->event_list_lock);
>+ mutex_lock(&ev_int->event_list_lock);
>+ if (test_and_set_bit(IIO_BUSY_BIT_POS, &ev_int->flags)) {
>+ mutex_unlock(&ev_int->event_list_lock);
> return -EBUSY;
> }
>- mutex_unlock(&indio_dev->event_interface->event_list_lock);
>- fd = anon_inode_getfd("iio:event",
>- &iio_event_chrdev_fileops,
>- indio_dev->event_interface, O_RDONLY);
>+ mutex_unlock(&ev_int->event_list_lock);
>+ fd = anon_inode_getfd("iio:event", &iio_event_chrdev_fileops,
>+ ev_int, O_RDONLY);
> if (fd < 0) {
>- mutex_lock(&indio_dev->event_interface->event_list_lock);
>+ mutex_lock(&ev_int->event_list_lock);
> clear_bit(IIO_BUSY_BIT_POS, &ev_int->flags);
>- mutex_unlock(&indio_dev->event_interface->event_list_lock);
>+ mutex_unlock(&ev_int->event_list_lock);
> }
> return fd;
> }
>--
>1.7.8.rc3
--
Sent from my Android phone
with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2011-11-24 8:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 10:13 Sasha Levin
2011-11-23 14:17 ` Dan Carpenter
2011-11-23 14:21 ` Sasha Levin
2011-11-24 8:49 ` Jonathan Cameron [this message]
2011-11-24 8:54 ` Sasha Levin
2011-11-24 9:11 ` Jonathan Cameron
2011-11-24 23:47 ` Stephen Rothwell
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=4e3c37a6-3777-4138-800b-f055f7caa8f3@email.android.com \
--to=jic23@cam.ac.uk \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=levinsasha928@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@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®