mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nicola Fiorillo <nicfio@gmail.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
	Hans Verkuil <hverkuil@kernel.org>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Nguyen Ngoc Thang <ngocthang2710.1999@gmail.com>,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	nicfio@gmail.com
Subject: Re: [PATCH v3 2/2] media: v4l2-subdev: Fix NULL pointer dereference in the EXT_CTRLS ioctls
Date: Thu, 08 Oct 2026 15:55:55 +0200	[thread overview]
Message-ID: <179146775576.53729.7241687195832895526@gmail.com> (raw)
In-Reply-To: <asdz93f28oRR-WPu@kekkonen.localdomain>

Hi Sakari,

On Thu, Oct 08, 2026 at 01:44:07PM +0300, Sakari Ailus wrote:
> Unregistering a sub-device node isn't doable safely currently. Addressing
> this properly requires much more than this patch does, and also I'm afraid
> this patch isn't part of properly addressing this either.

Understood. As I wrote to Laurent earlier today, I have withdrawn the
whole series: both patches only narrow the window, and the real issue is
the lifetime of the objects, not something more checks in the file
operations can fix.

Thank you and Laurent for taking the time to review it.

Thanks,
Nicola

      reply	other threads:[~2026-10-08 13:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-08  4:25 [PATCH v3 0/2] media: v4l2-subdev: Fix NULL dereferences racing with unbind Nicola Fiorillo
2026-10-08  4:25 ` [PATCH v3 1/2] media: v4l2-subdev: Fix NULL pointer dereference in subdev_open() Nicola Fiorillo
2026-10-08  5:48   ` Laurent Pinchart
2026-10-08  7:06     ` Nicola Fiorillo
2026-10-08  4:26 ` [PATCH v3 2/2] media: v4l2-subdev: Fix NULL pointer dereference in the EXT_CTRLS ioctls Nicola Fiorillo
2026-10-08 10:44   ` Sakari Ailus
2026-10-08 13:55     ` Nicola Fiorillo [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=179146775576.53729.7241687195832895526@gmail.com \
    --to=nicfio@gmail.com \
    --cc=hverkuil@kernel.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=ngocthang2710.1999@gmail.com \
    --cc=sakari.ailus@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®