mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Nicola Fiorillo <nicfio@gmail.com>
Cc: linux-media@vger.kernel.org, mchehab@kernel.org,
	hverkuil@kernel.org, antti.laakso@linux.intel.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] media: Two oopses and a hang when unbinding a streaming sensor
Date: Sat, 12 Sep 2026 13:23:42 +0300	[thread overview]
Message-ID: <aqUoLr0JFGEBiJIf@kekkonen.localdomain> (raw)
In-Reply-To: <20260911194854.78894-1-nicfio@gmail.com>

Hi Nicola,

On Fri, Sep 11, 2026 at 09:48:51PM +0200, Nicola Fiorillo wrote:
> Unbinding a camera sensor while a capture is running is a scenario that
> nothing in the IPU6 path handles: the kernel oopses twice, corrupts memory
> once, and leaves the application blocked forever. None of this is caused by
> the sensor drivers themselves, and all four failures are present in
> mainline today.

Thanks for the patchset. These are known issues and unfortunately unbinding
drivers while streaming isn't supported on MC-enabled drivers currently.
This is a MC/V4L2 framework limitation and cannot be meaningfully worked
around in drivers.

-- 
Kind regards,

Sakari Ailus

  parent reply	other threads:[~2026-09-12 10:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-11 19:48 Nicola Fiorillo
2026-09-11 19:48 ` [PATCH v2 1/3] media: ipu6: Check the remote pad before dereferencing it Nicola Fiorillo
2026-09-11 19:48 ` [PATCH v2 2/3] media: v4l2-subdev: Check v4l2_dev before dereferencing it in open() Nicola Fiorillo
2026-09-11 19:48 ` [PATCH v2 3/3] media: ipu6: Signal the video queues when a sensor is unbound Nicola Fiorillo
2026-09-12 10:23 ` Sakari Ailus [this message]
2026-09-12 11:20   ` [PATCH v2 0/3] media: Two oopses and a hang when unbinding a streaming sensor Nicola Fiorillo
2026-10-01 17:27     ` Nicola Fiorillo

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=aqUoLr0JFGEBiJIf@kekkonen.localdomain \
    --to=sakari.ailus@linux.intel.com \
    --cc=antti.laakso@linux.intel.com \
    --cc=hverkuil@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=nicfio@gmail.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®