Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] CBS
Date: Tue, 6 Aug 2024 20:12:53 +0200
Message-ID: <20240806181253.GK4991@pb2> (raw)
In-Reply-To: <AS8P250MB0744FB97065C8F8CC2CB22908FBF2@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM>


[-- Attachment #1.1: Type: text/plain, Size: 2879 bytes --]

On Tue, Aug 06, 2024 at 07:54:58PM +0200, Andreas Rheinhardt wrote:
> Michael Niedermayer:
> > On Tue, Aug 06, 2024 at 07:05:38PM +0200, Michael Niedermayer wrote:
> >> Hi
> >>
> >> Did CBS win the obfuscated C contest yet?
> >>
> >> I was just looking at a msan issue and then looked at this:
> >>
> >> CHECK(FUNC_SEI(message_list)(ctx, rw, &current->message_list, 1));
> >>
> >>
> >> #define CHECK(call) do { \
> >>         err = (call); \
> >>         if (err < 0) \
> >>             return err; \
> >>     } while (0)
> >>
> >> #define FUNC_NAME2(rw, codec, name) cbs_ ## codec ## _ ## rw ## _ ## name
> >> #define FUNC_NAME1(rw, codec, name) FUNC_NAME2(rw, codec, name)
> >> #define FUNC_H264(name) FUNC_NAME1(READWRITE, h264, name)
> >> #define FUNC_H265(name) FUNC_NAME1(READWRITE, h265, name)
> >> #define FUNC_H266(name) FUNC_NAME1(READWRITE, h266, name)
> >> #define FUNC_SEI(name)  FUNC_NAME1(READWRITE, sei,  name)
> >>
> >> #define SEI_FUNC(name, args) \
> >> static int FUNC(name) args;  \
> >> static int FUNC(name ## _internal)(CodedBitstreamContext *ctx, \
> >>                                    RWContext *rw, void *cur,   \
> >>                                    SEIMessageState *state)     \
> >> { \
> >>     return FUNC(name)(ctx, rw, cur, state); \
> >> } \
> >> static int FUNC(name) args
> >>
> >>
> >> anyway, can we remove all preprocessor use from cbs ?
> 
> I don't think that this is really obfuscated.

Then you qualify as maintainer for this code.
Thanks!


> 
> > 
> > the issue iam looking at is due to
> > 
> > SEI_FUNC(sei_pic_timing, (CodedBitstreamContext *ctx, RWContext *rw, H264RawSEIPicTiming *current, SEIMessageState *sei))
> > 
> > having different active SPS on writing than reading, so the write code
> > has nal_hrd_parameters_present_flag set while the read had that 0
> > so uninitialized data is written
> > 
> > I cannot find any match for "cbs" in MAINTAINERS, also there are no copyright
> > with names in the cbs code.
> 
> 1. I just sent a patch that "fixes" this.

Thats what i came up with too (and it works). Given we both hit that,
please apply


> 2. But actually, there is a deeper bug here: We would need to defer
> parsing certain SEI message units to a second pass when the currently
> active SPS is known. This can happen with spec-compliant input (and even
> more so with spec-incompliant input, which is presumably what the fuzzer
> produced).

Thats a deeper analysis than what i did. I stoped at the "just clear it, as in 1."
and then was looking for someone who would implement the correct fix

Ill send you the input sample privately

Thanks alot!

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

The educated differ from the uneducated as much as the living from the
dead. -- Aristotle 

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

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

      parent reply	other threads:[~2024-08-06 18:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-06 17:05 Michael Niedermayer
2024-08-06 17:38 ` Michael Niedermayer
2024-08-06 17:54   ` Andreas Rheinhardt
2024-08-06 18:04     ` James Almer
2024-08-06 18:41       ` Andreas Rheinhardt
2024-08-06 19:12         ` Michael Niedermayer
2024-08-06 19:51           ` Andreas Rheinhardt
2024-08-06 22:11             ` Michael Niedermayer
2024-08-06 18:12     ` Michael Niedermayer [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=20240806181253.GK4991@pb2 \
    --to=michael@niedermayer.cc \
    --cc=ffmpeg-devel@ffmpeg.org \
    /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

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git