From: Jonathan Cameron <jic23@kernel.org>
To: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
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 0/7] HID: sensor: custom: use-after-freec after remove
Date: Sat, 7 Nov 2026 20:08:40 +0000 [thread overview]
Message-ID: <20261107200840.2de08565@jic23-hlaptop> (raw)
In-Reply-To: <20261104201403.2039921-1-srinivas.pandruvada@linux.intel.com>
On Wed, 4 Nov 2026 12:13:56 -0800
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com> wrote:
Trivial but freec in the title. If we end up having a v3, please
tidy that up.,
> This is v2 for patch " [PATCH] HID: sensor-custom: Synchronize
> misc-device teardown with file lifetime".
>
> This patch series is essentially the same version that was sent to
> Семён for testing.
>
> Following a feedback review conducted with various AI models, it was
> suggested to break each change into individual, separate patches. This
> makes perfect sense, which is why this series now contains more patches.
>
> Additionally, these reviews identified issues in the adjacent probe and
> removal code when active sensor instances are present. I have addressed
> those issues in this version as well.
>
> Srinivas Pandruvada (7):
> HID: sensor: hub: Synchronize callback removal with raw events
> HID: sensor: custom: Set owner for misc device
> HID: sensor: custom: Disable sensor before hub close on removal
> HID: sensor: custom: Fix state lifetime during removal
> HID: sensor: custom: Serialize misc device reads
> HID: sensor: custom: Register enable attribute after misc device
> HID: sensor: hub: Remove clients before stopping hardware
>
> drivers/hid/hid-sensor-custom.c | 121 +++++++++++++++++++++++---------
> drivers/hid/hid-sensor-hub.c | 27 +++++--
> 2 files changed, 110 insertions(+), 38 deletions(-)
>
prev parent reply other threads:[~2026-11-07 20:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 20:13 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-07 20:16 ` Jonathan Cameron
2026-11-04 20:14 ` [PATCH v2 7/7] HID: sensor: hub: Remove clients before stopping hardware Srinivas Pandruvada
2026-11-07 20:08 ` Jonathan Cameron [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=20261107200840.2de08565@jic23-hlaptop \
--to=jic23@kernel.org \
--cc=bentiss@kernel.org \
--cc=crofts@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 \
--cc=srinivas.pandruvada@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®