linux-kernel - Re: [PATCH] media: coda: Keep metas sync with hardware fifo

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 11 Nov 2021 18:03:01 +0100
From:   Philipp Zabel <p.zabel@...gutronix.de>
To:     Benjamin Gaignard <benjamin.gaignard@...labora.com>,
        mchehab@...nel.org
Cc:     linux-media@...r.kernel.org, linux-kernel@...r.kernel.org,
        kernel@...labora.com
Subject: Re: [PATCH] media: coda: Keep metas sync with hardware fifo

Hi Benjamin,

On Mon, 2021-11-08 at 15:24 +0100, Benjamin Gaignard wrote:
> After updating the output fifo position be sure that metas are also
> synchronised with this position.
> 
> Signed-off-by: Benjamin Gaignard <benjamin.gaignard@...labora.com>
> ---
>  drivers/media/platform/coda/coda-bit.c | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/drivers/media/platform/coda/coda-bit.c b/drivers/media/platform/coda/coda-bit.c
> index c484c008ab02..28c56286b0de 100644
> --- a/drivers/media/platform/coda/coda-bit.c
> +++ b/drivers/media/platform/coda/coda-bit.c
> @@ -2315,6 +2315,12 @@ static void coda_finish_decode(struct coda_ctx *ctx)
>  	/* Update kfifo out pointer from coda bitstream read pointer */
>  	coda_kfifo_sync_from_device(ctx);
>
> +	/*
> +	 * After updating the read pointer, we need to check if
> +	 * any metas are consumed and should be released.
> +	 */
> +	coda_decoder_drop_used_metas(ctx);
> +

This doesn't look right. If you drop all metas seen by the decoder right
away, they can't be copied into the decoded picture's meta slot later in
this function. I'd expect you run into the "empty timestamp list!"
errors if you do this.

regards
Philipp