From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: jikos@kernel.org, bentiss@kernel.org,
linux-input@vger.kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, simeon@maryasin.name,
lixu.zhang@intel.com, crofts@kernel.org
Subject: Re: [PATCH v2 6/7] HID: sensor: custom: Register enable attribute after misc device
Date: Sun, 08 Nov 2026 16:47:27 -0800 [thread overview]
Message-ID: <b83129fac311b72376cb6fcef5448d3b66c3b45b.camel@linux.intel.com> (raw)
In-Reply-To: <20261107201601.7d5aa69f@jic23-hlaptop>
On Sat, 2026-11-07 at 20:16 +0000, Jonathan Cameron wrote:
> On Wed, 4 Nov 2026 12:14:02 -0800
> Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com> wrote:
>
> > Register the enable_sensor sysfs group only after misc-device setup
> > succeeds. This prevents userspace from opening the sensor hub while
> > probe can still fail, which would otherwise leave the hub open
> > reference
> > unbalanced on unwind.
> >
> > Fixes: 4a7de0519df5 ("HID: sensor: Custom and Generic sensor
> > support")
> > Reported-by: Семён Марьясин <simeon@maryasin.name>
> > Closes:
> > https://lore.kernel.org/all/CAM2dg7ewfVJSP4rFyhkCB1Rmd1+X56sAg=eUdbPthG2xrLqwQQ@mail.gmail.com/
> > Signed-off-by: Srinivas Pandruvada
> > <srinivas.pandruvada@linux.intel.com>
> You probably already saw it, but sashiko had more feedback.
> https://sashiko.dev/#/patchset/20261104201403.2039921-1-srinivas.pandruvada%40linux.intel.com
>
> I haven't looked closely at it though so might be either wrong
> or material for a future patch.
>
> One rather odd looking thing in here though.
>
>
> > ---
> > drivers/hid/hid-sensor-custom.c | 15 ++++++++-------
> > 1 file changed, 8 insertions(+), 7 deletions(-)
> >
> > diff --git a/drivers/hid/hid-sensor-custom.c b/drivers/hid/hid-
> > sensor-custom.c
> > index 4f824cadd370..990e653995e1 100644
> > --- a/drivers/hid/hid-sensor-custom.c
> > +++ b/drivers/hid/hid-sensor-custom.c
> > @@ -1059,20 +1059,21 @@ static int hid_sensor_custom_probe(struct
> > platform_device *pdev)
> > if (ret)
> > goto err_remove_callback;
> >
> > - ret = sysfs_create_group(&sensor_inst->pdev->dev.kobj,
> > - &enable_sensor_attr_group);
> > + ret = hid_sensor_custom_dev_if_add(sensor_inst);
> > if (ret)
> > goto err_remove_attributes;
> >
> > - ret = hid_sensor_custom_dev_if_add(sensor_inst);
> > + ret = sysfs_create_group(&sensor_inst->pdev->dev.kobj,
> > + &enable_sensor_attr_group);
> > if (ret)
> > - goto err_remove_group;
> > + goto err_remove_dev_if;
> >
> > return 0;
> >
> > -err_remove_group:
> > - sysfs_remove_group(&sensor_inst->pdev->dev.kobj,
> > - &enable_sensor_attr_group);
> > +err_remove_dev_if:
> > + sensor_hub_remove_callback(hsdev, hsdev->usage);
> > + hid_sensor_custom_dev_if_remove(sensor_inst);
> > + goto err_remove_attributes;
>
> If my eyes are tricking me, isn't this going to the next line?
I realized that. Will fix this in next update.
Thanks,
Srinivas
>
> > err_remove_attributes:
> > hid_sensor_custom_remove_attributes(sensor_inst);
> > err_remove_callback:
next prev parent reply other threads:[~2026-11-09 0:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 20:13 [PATCH v2 0/7] HID: sensor: custom: use-after-freec after remove Srinivas Pandruvada
2026-11-04 20:13 ` [PATCH v2 1/7] HID: sensor: hub: Synchronize callback removal with raw events Srinivas Pandruvada
2026-11-05 9:56 ` Joshua Crofts
2026-11-07 20:13 ` Jonathan Cameron
2026-11-04 20:13 ` [PATCH v2 2/7] HID: sensor: custom: Set owner for misc device Srinivas Pandruvada
2026-11-05 9:57 ` Joshua Crofts
2026-11-04 20:13 ` [PATCH v2 3/7] HID: sensor: custom: Disable sensor before hub close on removal Srinivas Pandruvada
2026-11-05 10:21 ` Joshua Crofts
2026-11-04 20:14 ` [PATCH v2 4/7] HID: sensor: custom: Fix state lifetime during removal Srinivas Pandruvada
2026-11-07 20:21 ` Jonathan Cameron
2026-11-04 20:14 ` [PATCH v2 5/7] HID: sensor: custom: Serialize misc device reads Srinivas Pandruvada
2026-11-04 20:14 ` [PATCH v2 6/7] HID: sensor: custom: Register enable attribute after misc device Srinivas Pandruvada
2026-11-04 20:25 ` sashiko-bot
2026-11-04 22:04 ` srinivas pandruvada
2026-11-07 20:16 ` Jonathan Cameron
2026-11-09 0:47 ` Srinivas Pandruvada [this message]
2026-11-04 20:14 ` [PATCH v2 7/7] HID: sensor: hub: Remove clients before stopping hardware Srinivas Pandruvada
2026-11-07 20:08 ` [PATCH v2 0/7] HID: sensor: custom: use-after-freec after remove Jonathan Cameron
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=b83129fac311b72376cb6fcef5448d3b66c3b45b.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=bentiss@kernel.org \
--cc=crofts@kernel.org \
--cc=jic23@kernel.org \
--cc=jikos@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lixu.zhang@intel.com \
--cc=simeon@maryasin.name \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox