From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Jonathan Cameron <jic23@kernel.org>, Felipe Balbi <balbi@ti.com>,
linux-iio@vger.kernel.org
Subject: Re: [PATCH 1/2] iio: adc: ti_am335x_adc: do not free the kfifo twice
Date: Thu, 24 Oct 2013 12:51:01 +0200 [thread overview]
Message-ID: <5268FB95.7010601@linutronix.de> (raw)
In-Reply-To: <5268F9F7.5020701@metafoo.de>
On 10/24/2013 12:44 PM, Lars-Peter Clausen wrote:
>> Shouldn't the two
>>
>> tiadc_iio_buffered_hardware_remove(indio_dev);
>> tiadc_channels_remove(indio_dev);
>>
>> in tiadc_remove() be reversed in their call order? The second alter is
>> accessing the buffer which is released by the former one.
>>
>
> As far as I can see tiadc_channels_remove() only does a
> kfree(indio_dev->channels), so it does not access the buffer at all.
I'm sorry I meant
iio_kfifo_free(indio_dev->buffer);
iio_buffer_unregister(indio_dev);
in tiadc_iio_buffered_hardware_remove()
>> btw: is all this ref counting really required? I mean I would assume
>> allocate buffer in one place (at probe time) release it remove time
>> should be enough.
>
> It is required. Userspace may still be reading from the buffer when the
> driver frees it. So we need proper refcounting here.
Ach okay then.
Sebastian
next prev parent reply other threads:[~2013-10-24 10:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-23 17:44 [PATCH 1/2] iio: adc: ti_am335x_adc: do not free the kfifo twice Lars-Peter Clausen
2013-10-24 10:13 ` Jonathan Cameron
2013-10-24 9:25 ` Sebastian Andrzej Siewior
2013-10-24 9:41 ` Lars-Peter Clausen
2013-10-24 10:34 ` Sebastian Andrzej Siewior
2013-10-24 10:44 ` Lars-Peter Clausen
2013-10-24 10:51 ` Sebastian Andrzej Siewior [this message]
2013-10-24 11:50 ` Jonathan Cameron
2013-11-09 12:34 ` Jonathan Cameron
2013-11-10 9:37 ` Lars-Peter Clausen
2013-11-10 11:31 ` Jonathan Cameron
-- strict thread matches above, loose matches on Subject: below --
2013-10-23 17:00 Sebastian Andrzej Siewior
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=5268FB95.7010601@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=balbi@ti.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.