mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: jikos@kernel.org, jic23@kernel.org, bentiss@kernel.org
Cc: 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,
	Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Subject: [PATCH v3 0/7] HID: sensor: custom: use-after-free after remove
Date: Mon,  9 Nov 2026 11:59:42 -0800	[thread overview]
Message-ID: <20261109195949.384888-1-srinivas.pandruvada@linux.intel.com> (raw)

This is v3 version with changes suggested by shashiko-bot and Jonathan.
Also rebased on top of 7.4-rc2 kernel release.

This patch series is essentially the same version that was sent to
Semyon 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.

v3:
- Address comment on patch 6/7 by Shashiko on useless goto
and suggestion to remove sensor_hub_remove_callback() for
err_remove_dev_if.
- On patch 4/7 : HID: sensor: custom: Fix state lifetime during removal
Rename goto as suggested by Jonathan

For using guard(), need a follow up patch as that will be a cleanup.


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 | 118 +++++++++++++++++++++++---------
 drivers/hid/hid-sensor-hub.c    |  27 ++++++--
 2 files changed, 108 insertions(+), 37 deletions(-)

-- 
2.56.0


             reply	other threads:[~2026-11-09 19:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-09 19:59 Srinivas Pandruvada [this message]
2026-11-09 19:59 ` [PATCH v3 1/7] HID: sensor-hub: Synchronize callback removal with raw events Srinivas Pandruvada
2026-11-09 19:59 ` [PATCH v3 2/7] HID: sensor: custom: Set owner for misc device Srinivas Pandruvada
2026-11-09 19:59 ` [PATCH v3 3/7] HID: sensor: custom: Disable sensor before hub close on removal Srinivas Pandruvada
2026-11-09 19:59 ` [PATCH v3 4/7] HID: sensor: custom: Fix state lifetime during removal Srinivas Pandruvada
2026-11-09 19:59 ` [PATCH v3 5/7] HID: sensor: custom: Serialize misc device reads Srinivas Pandruvada
2026-11-09 19:59 ` [PATCH v3 6/7] HID: sensor: custom: Register enable attribute after misc device Srinivas Pandruvada
2026-11-09 19:59 ` [PATCH v3 7/7] HID: sensor-hub: Remove clients before stopping hardware Srinivas Pandruvada

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=20261109195949.384888-1-srinivas.pandruvada@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

all inboxes | Powered by JetHome®