From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.ffmpeg.org (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTPS id 601E14C760 for ; Wed, 25 Jun 2025 21:39:28 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTP id A3C2A68DB66; Thu, 26 Jun 2025 00:39:25 +0300 (EEST) Date: Wed, 25 Jun 2025 21:39:16 +0000 To: FFmpeg development discussions and patches In-Reply-To: References: MIME-Version: 1.0 Message-ID: List-Id: FFmpeg development discussions and patches List-Post: From: Tristan Matthews via ffmpeg-devel Precedence: list Cc: Tristan Matthews X-Mailman-Version: 2.1.29 X-BeenThere: ffmpeg-devel@ffmpeg.org List-Subscribe: , List-Unsubscribe: , List-Archive: Reply-To: FFmpeg development discussions and patches List-Help: Subject: Re: [FFmpeg-devel] [PATCH] checkasm/h264dsp: Fix stack-buffer-overflow, effective-type violations Content-Type: multipart/mixed; boundary="===============8119603998376164440==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============8119603998376164440== Content-Type: message/rfc822 Content-Disposition: inline Return-Path: X-Original-To: ffmpeg-devel@ffmpeg.org Delivered-To: ffmpeg-devel@ffmpeg.org Received: from mail-106103.protonmail.ch (mail-106103.protonmail.ch [79.135.106.103]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTPS id 34A8768D086 for ; Thu, 26 Jun 2025 00:39:19 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1750887558; x=1751146758; bh=WOmlG62Wj3d9GejwolblfgBWSWWcxQPSRAU0nnHGatk=; h=Date:To:From:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=kR1dsQPBWZdMW/rfmSWZ2ojTPmz7UaRoyySjBBxMNcGvS9ddjGWDbxqkKHp5mdyGi YQN7lxcz1/9sMRbc4zVLvcnV1v8+Py2fjB/7DyU3zRp5ysptjAXDtz8IPwv6QbcVsu tTjEHN3iT4RNVyHIfonnHm77/fbVSjdyA6u3OkZoTHDVfLxXByNvuXSj10faKnehSy jYUBLYNO8GsyCDqVUysy2AfovhAdAtJxd9ClIXjx583ilwcsl5GHvR7HDfoFOxkxoN KyJddLQ8hWS9gjB2qEQKII32E/jjYS4I5EKFYf2DaoWuEs07Ton4Wp4gROTt6YxCut Py8Q8iA3SLC9w== Date: Wed, 25 Jun 2025 21:39:16 +0000 To: FFmpeg development discussions and patches From: Tristan Matthews Subject: Re: [FFmpeg-devel] [PATCH] checkasm/h264dsp: Fix stack-buffer-overflow, effective-type violations Message-ID: In-Reply-To: References: Feedback-ID: 32895411:user:proton X-Pm-Message-ID: 5d5a4efaa5c5b6bf7cf5907e63c0e4e5796a6dcd MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On Monday, June 16th, 2025 at 2:22 PM, Andreas Rheinhardt wrote: > Tristan Matthews via ffmpeg-devel: >=20 > > On Monday, June 16th, 2025 at 6:53 AM, Andreas Rheinhardt andreas.rhein= hardt@outlook.com wrote: > >=20 > > > Patch attached. > >=20 > > LGTM, and sorry about that, for future reference did you do anything in= particular (instrumentation wise) to catch the stack overflow? I tried mak= e fate on a few different machines and didn't hit that. > >=20 > > Best, > > Tristan >=20 >=20 > I used (Clang) ASAN. Presumably Zhao Zhili (who first reported the stack > buffer overflow) did so, too. >=20 > - Andreas >=20 It'd be good to merge either this or Zhao Zhili's patch to get checkasm bac= k to being ASAN clean. Best, Tristan --===============8119603998376164440== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 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". --===============8119603998376164440==--