[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220530153044.y4r4zmxdbyev3tla@CAB-WSD-L081021.sigma.sbrf.ru>
Date: Mon, 30 May 2022 15:29:57 +0000
From: Dmitry Rokosov <DDRokosov@...rdevices.ru>
To: Jonathan Cameron <jic23@...nel.org>
CC: "robh+dt@...nel.org" <robh+dt@...nel.org>,
"lars@...afoo.de" <lars@...afoo.de>,
"andy.shevchenko@...il.com" <andy.shevchenko@...il.com>,
"lorenzo.bianconi83@...il.com" <lorenzo.bianconi83@...il.com>,
"srinivas.pandruvada@...ux.intel.com"
<srinivas.pandruvada@...ux.intel.com>,
"teodora.baluta@...el.com" <teodora.baluta@...el.com>,
"narcisaanamaria12@...il.com" <narcisaanamaria12@...il.com>,
"linux-iio@...r.kernel.org" <linux-iio@...r.kernel.org>,
kernel <kernel@...rdevices.ru>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 0/5] iio: treewide: rearrange iio trig get/register
Jonathan,
On Sat, May 28, 2022 at 06:10:04PM +0100, Jonathan Cameron wrote:
> > If this call order is wrong, the next iio_trigger_put() (from sysfs
> > callback or "delete module" path) will dereference "default" module
> > refcnt, which is incorrect behaviour.
>
> Hi Dmitry,
>
> Series applied to the fixes-togreg branch of iio.git and marked for stable.
>
Thank you!
> Do you think it's also worth adding a runtime warning in iio_trigger_get()
> on !trig->owner so that we catch any cases of this introduced in the future?
>
Good point, it will help other kernel developers to avoid such mistake.
I'll prepare new patchset with that.
--
Thank you,
Dmitry
Powered by blists - more mailing lists