From: Tomasz Duszynski <tomasz.duszynski@octakon.com>
To: Alexandru Ardelean <ardeleanalex@gmail.com>
Cc: Tomasz Duszynski <tomasz.duszynski@octakon.com>,
linux-iio <linux-iio@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH] iio: core: fix ioctl handlers removal
Date: Fri, 23 Apr 2021 10:00:23 +0200 [thread overview]
Message-ID: <YIJ+l4ScIua4RBKt@arch> (raw)
In-Reply-To: <CA+U=DsqQUse-cP7k+42reHPYfbAUMTsqLst5--BHKg53FhNbxg@mail.gmail.com>
On Fri, Apr 23, 2021 at 10:17:42AM +0300, Alexandru Ardelean wrote:
> On Thu, Apr 22, 2021 at 11:26 PM Tomasz Duszynski
> <tomasz.duszynski@octakon.com> wrote:
> >
> > Currently ioctl handlers are removed twice. For the first time during
> > iio_device_unregister() then later on inside
> > iio_device_unregister_eventset() and iio_buffers_free_sysfs_and_mask().
> > Double free leads to kernel panic.
> >
> > Fix this by not touching ioctl handlers list directly but rather
> > letting code responsible for registration call the matching cleanup
> > routine itself.
> >
>
> This change is missing this tag:
>
> Fixes: 8dedcc3eee3ac ("iio: core: centralize ioctl() calls to the main chardev")
>
> With that tag added:
> Acked-by: Alexandru Ardelean <ardeleanalex@gmail.com>
>
> Apologies for the breakage.
No worries. Will append you ack to v2 then.
> Also, I wasn't sure if Jonathan or anyone else wanted to do this change.
>
> Thanks for the patch
> Alex
>
> > Signed-off-by: Tomasz Duszynski <tomasz.duszynski@octakon.com>
> > ---
> > drivers/iio/industrialio-core.c | 3 ---
> > 1 file changed, 3 deletions(-)
> >
> > diff --git a/drivers/iio/industrialio-core.c b/drivers/iio/industrialio-core.c
> > index d92c58a94fe4..98944cfc7331 100644
> > --- a/drivers/iio/industrialio-core.c
> > +++ b/drivers/iio/industrialio-core.c
> > @@ -1939,9 +1939,6 @@ void iio_device_unregister(struct iio_dev *indio_dev)
> >
> > indio_dev->info = NULL;
> >
> > - list_for_each_entry_safe(h, t, &iio_dev_opaque->ioctl_handlers, entry)
> > - list_del(&h->entry);
> > -
> > iio_device_wakeup_eventset(indio_dev);
> > iio_buffer_wakeup_poll(indio_dev);
> >
> > --
> > 2.31.1
> >
prev parent reply other threads:[~2021-04-23 8:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 20:14 [PATCH] iio: core: fix ioctl handlers removal Tomasz Duszynski
2021-04-23 7:17 ` Alexandru Ardelean
2021-04-23 8:00 ` Tomasz Duszynski [this message]
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=YIJ+l4ScIua4RBKt@arch \
--to=tomasz.duszynski@octakon.com \
--cc=ardeleanalex@gmail.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--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 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.