[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d45245cd-5950-ce98-eebe-49f0d5fa95bb@intel.com>
Date: Tue, 24 May 2016 15:33:45 +0300
From: Crestez Dan Leonard <leonard.crestez@...el.com>
To: Linus Walleij <linus.walleij@...aro.org>
Cc: Jonathan Cameron <jic23@...nel.org>,
"linux-iio@...r.kernel.org" <linux-iio@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Hartmut Knaack <knaack.h@....de>,
Lars-Peter Clausen <lars@...afoo.de>,
Peter Meerwald-Stadler <pmeerw@...erw.net>,
Daniel Baluta <daniel.baluta@...el.com>,
Giuseppe Barba <giuseppe.barba@...com>,
Denis Ciocca <denis.ciocca@...com>
Subject: Re: [PATCH 1/3] iio: st_sensors: Init trigger before irq request
On 05/24/2016 02:27 PM, Linus Walleij wrote:
> On Fri, May 13, 2016 at 8:43 PM, Crestez Dan Leonard
> <leonard.crestez@...el.com> wrote:
>
>> This fixes a possible race where an interrupt arrives before complete
>> initialization and crashes because iio_trigger_get_drvdata returns NULL.
>>
>> Cc: Linus Walleij <linus.walleij@...aro.org>
>> Cc: Giuseppe Barba <giuseppe.barba@...com>
>> Cc: Denis Ciocca <denis.ciocca@...com>
>> Signed-off-by: Crestez Dan Leonard <leonard.crestez@...el.com>
>> ---
>> I ran into this while breaking the driver. But since the interrupt line can be
>> shared the handler should always be able to accept and ignore a call.
>
> Reviewed-by: Linus Walleij <linus.walleij@...aro.org>
>
> However I think my patch fixing the thread issue will collide
> by being close in context to this so it'd be great if you
> could resend it on top of
> "iio: st_sensors: switch to a threaded interrupt"?
I checked my local git tree and this was already on top of v6 of that
patch. I think this issue is much less likely to cause problems without
it. Perhaps it should be incorporated into your patch?
I'll resend if it causes conflicts for Jonathan.
--
Regards,
Leonard
Powered by blists - more mailing lists