All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Richard Weinberger <richard@nod.at>, harald@ccbib.org
Cc: knaack.h@gmx.de, lars@metafoo.de, pmeerw@pmeerw.net,
	sanjeev_sharma@mentor.com, linux-iio@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: iio: dht11 Updates
Date: Sun, 04 Jan 2015 11:01:53 +0000	[thread overview]
Message-ID: <54A91DA1.6080107@kernel.org> (raw)
In-Reply-To: <54A680F8.30209@nod.at>

On 02/01/15 11:28, Richard Weinberger wrote:
> Am 01.01.2015 um 22:18 schrieb harald@ccbib.org:
>> Hi!
>>
>> On Thu, 01 Jan 2015 12:38:23 +0000, Jonathan Cameron <jic23@kernel.org>
>> wrote:
>>> On 02/12/14 23:32, Richard Weinberger wrote:
>>>> Please see my current patches for your driver.
>>>> As discussed in an earlier mail I'm testing with the DHT22 sensor only.
>>>> With the IRQ changes I see 84 edges.
>>>>
>>>>
>>>> [PATCH 1/4] iio: dht11: Add locking
>>>> [PATCH 2/4] iio: dht11: IRQ fixes
>>>> [PATCH 3/4] iio: dht11: Logging updates
>>>> [PATCH 4/4] iio: dht11: Fix out-of-bounds read
>>>>
>>  
>>> I've lost track of where we are with this patch series.
>>> Does this cause trouble on any of the parts supported?
>>
>> Yes, 2/4 needs an update. 
> 
> Correct.
> 
>> 1/4 is fine by me, however it was noted that there is already
>> locking in the iio core for the in-kernel interface but not
>> for the sysfs interface. I think we need locking in the case of
>> the sysfs interace as well, but the final decision is yours...
> 
> We definitely need it.
> I have more than one sensor attached and collectd queries them.
> Without locking collectd manages to hit this race window.
> So the issue is real.
Locking is needed.  Convention has normally been to do this in the
driver rather than a subsystem core.
That gives more fine grained control and avoids locking
when not necessary (some devices will need a lock on data read,
others will not).
Clearly in this case, the need should have been picked up in review
(oops).  Sorry about that.
> 
>> 4/4 is obviously right.
>>
>> 3/4 is cleanup. I'd rather defer this to later and do it right,
>> because right now this patch is cosmetic and doesn't get rid of
>> the deeper issues. I'll start to work on a cleanup series once
>> the fixes are merged.
> 
> Agreed.
> 
>> Richard, what's your timeframe to send an updated series?
>> I can send an update if you don't have time.
> 
> It would be great if you can send an updated version of 2/4.
> I don't have a DHT11 sensor (only DHT22) and I'm still recovering
> from a cold.
> 
> Thanks
> //richard
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


  reply	other threads:[~2015-01-04 11:01 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-02 23:32 iio: dht11 Updates Richard Weinberger
2014-12-02 23:32 ` [PATCH 1/4] iio: dht11: Add locking Richard Weinberger
2014-12-14 12:31   ` Hartmut Knaack
2014-12-14 14:06     ` Richard Weinberger
2014-12-02 23:32 ` [PATCH 2/4] iio: dht11: IRQ fixes Richard Weinberger
2014-12-02 23:35   ` Richard Weinberger
2014-12-06 17:21   ` harald
2014-12-02 23:32 ` [PATCH 3/4] iio: dht11: Logging updates Richard Weinberger
2014-12-03 12:58   ` Harald Geyer
2014-12-03 13:11     ` Richard Weinberger
2014-12-03 13:56       ` Harald Geyer
2014-12-03 21:30         ` Richard Weinberger
2014-12-04 14:25           ` Harald Geyer
2014-12-02 23:32 ` [PATCH 4/4] iio: dht11: Fix out-of-bounds read Richard Weinberger
2014-12-14 12:32   ` Hartmut Knaack
2014-12-03 12:18 ` iio: dht11 Updates Harald Geyer
2014-12-03 13:15   ` Richard Weinberger
2014-12-03 14:08     ` Harald Geyer
2014-12-03 14:29       ` Richard Weinberger
2014-12-03 22:05       ` Richard Weinberger
2014-12-04 13:45         ` Harald Geyer
2014-12-04 14:15           ` Richard Weinberger
2014-12-03 20:20   ` Richard Weinberger
2014-12-04 16:08     ` Harald Geyer
2015-01-01 12:38 ` Jonathan Cameron
2015-01-01 21:18   ` harald
2015-01-02 11:28     ` Richard Weinberger
2015-01-04 11:01       ` Jonathan Cameron [this message]
2015-01-05 13:49         ` [PATCHv2 1/3] iio: dht11: Fix out-of-bounds read Harald Geyer
2015-01-05 13:55           ` Richard Weinberger
2015-01-06  5:39             ` sanjeev sharma
2015-01-07 12:15             ` [PATCHv2 1/3,RESEND] " Harald Geyer
2015-01-10 11:14               ` Jonathan Cameron
2015-01-10 18:39                 ` Richard Weinberger
2015-01-12 11:26                   ` Harald Geyer
2015-01-12 11:27                     ` Richard Weinberger
2015-01-07 12:18             ` [PATCHv2 2/3,RESEND] iio: dht11: Add locking Harald Geyer
2015-01-10 11:16               ` Jonathan Cameron
2015-02-22 10:44                 ` Richard Weinberger
2015-02-25 12:01                   ` Jonathan Cameron
2015-01-07 12:22             ` [PATCHv2 3/3,RESEND] iio: dht11: IRQ fixes Harald Geyer

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=54A91DA1.6080107@kernel.org \
    --to=jic23@kernel.org \
    --cc=harald@ccbib.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmeerw@pmeerw.net \
    --cc=richard@nod.at \
    --cc=sanjeev_sharma@mentor.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 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.