public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Kocialkowski <paulk@sys-base.io>
To: Nicolas Dufresne <nicolas.dufresne@collabora.com>
Cc: Pengpeng Hou <pengpeng@iscas.ac.cn>,
	mchehab@kernel.org, hverkuil@kernel.org,
	sakari.ailus@linux.intel.com, laurent.pinchart@ideasonboard.com,
	opensource206@gmail.com, jernej.skrabec@gmail.com,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] media: v4l2-ctrls: validate HEVC slice reference lists
Date: Thu, 9 Apr 2026 15:52:31 +0200	[thread overview]
Message-ID: <adevHyqtwtEj2_-l@shepard> (raw)
In-Reply-To: <176cfd181e783d2b24fad1a2c7b18425374b4622.camel@collabora.com>

[-- Attachment #1: Type: text/plain, Size: 2066 bytes --]

Hi Nicolas,

On Mon 23 Mar 26, 09:41, Nicolas Dufresne wrote:
> > +
> > +		for (i = 0; i <= p_hevc_slice_params->num_ref_idx_l0_active_minus1;
> > +		     i++)
> > +			if (p_hevc_slice_params->ref_idx_l0[i] >=
> > +			    V4L2_HEVC_DPB_ENTRIES_NUM_MAX)
> > +				return -EINVAL;
> 
> That one is a breaking change since userspace already passes off limit values
> such as 0xff when a reference is missing (was lost). See:
> 
> 	47825b1646a6a9eca0f90baa3d4f98947c2add96
> 
> The hardware may or may not be capable of doing concealment, but with this
> change, we bring down all drivers to failing the decode completely.

So while some decoders may be able to deal with missing references, it seems
that cedrus should still error out in that case. I don't think it will be very
happy if we configure the hardware with L0/L1 lists that don't match what was
used for the encode.

But maybe we could pick up another (existing or empty) reference to replace the
missing one, which would be better than failing to decode the frame. IMO this
would be best done by userspace, but maybe we'd need some indication to know
that the hardware cannot deal with missing references.

What do you think?

All the best,

Paul

> > +
> > +		if (p_hevc_slice_params->slice_type != V4L2_HEVC_SLICE_TYPE_B)
> > +			break;
> > +
> > +		if (p_hevc_slice_params->num_ref_idx_l1_active_minus1 >=
> > +		    V4L2_HEVC_DPB_ENTRIES_NUM_MAX)
> > +			return -EINVAL;
> 
> Ack.
> 
> > +
> > +		for (i = 0; i <= p_hevc_slice_params->num_ref_idx_l1_active_minus1;
> > +		     i++)
> > +			if (p_hevc_slice_params->ref_idx_l1[i] >=
> > +			    V4L2_HEVC_DPB_ENTRIES_NUM_MAX)
> > +				return -EINVAL;
> 
> Same.
> 
> cheers,
> Nicolas
> 
> >  		break;
> >  
> >  	case V4L2_CTRL_TYPE_HEVC_EXT_SPS_ST_RPS:



-- 
Paul Kocialkowski,

Independent contractor - sys-base - https://www.sys-base.io/
Free software developer - https://www.paulk.fr/

Expert in multimedia, graphics and embedded hardware support with Linux.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2026-04-09 13:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-23  8:30 [PATCH v2] media: v4l2-ctrls: validate HEVC slice reference lists Pengpeng Hou
2026-03-23 13:41 ` Nicolas Dufresne
2026-04-09 13:52   ` Paul Kocialkowski [this message]
2026-04-09 14:14     ` Nicolas Dufresne
2026-04-09 14:44       ` Paul Kocialkowski
2026-03-23 20:36 ` kernel test robot
2026-03-23 20:36 ` kernel test robot
2026-03-24  3:13 ` Pengpeng Hou
2026-03-24  3:13 ` [PATCH v3] media: v4l2-ctrls: validate HEVC active reference counts Pengpeng Hou
2026-04-08 20:01   ` Nicolas Dufresne

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=adevHyqtwtEj2_-l@shepard \
    --to=paulk@sys-base.io \
    --cc=hverkuil@kernel.org \
    --cc=jernej.skrabec@gmail.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=nicolas.dufresne@collabora.com \
    --cc=opensource206@gmail.com \
    --cc=pengpeng@iscas.ac.cn \
    --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