Re: [FFmpeg-devel] [PATCH 2/5] checkasm/sw_scale: Fix stack-buffer-overflow

2020-05-20 Thread Andreas Rheinhardt
Michael Niedermayer: > On Tue, May 19, 2020 at 12:45:58PM +0200, Andreas Rheinhardt wrote: >> A buffer whose size is not a multiple of four has been initialized using >> consecutive writes of 32bits. This results in a stack-buffer-overflow >> reported by ASAN in the checkasm-sw_scale FATE-test. >>

Re: [FFmpeg-devel] [PATCH 2/5] checkasm/sw_scale: Fix stack-buffer-overflow

2020-05-20 Thread Michael Niedermayer
On Tue, May 19, 2020 at 12:45:58PM +0200, Andreas Rheinhardt wrote: > A buffer whose size is not a multiple of four has been initialized using > consecutive writes of 32bits. This results in a stack-buffer-overflow > reported by ASAN in the checkasm-sw_scale FATE-test. > > Signed-off-by: Andreas

[FFmpeg-devel] [PATCH 2/5] checkasm/sw_scale: Fix stack-buffer-overflow

2020-05-19 Thread Andreas Rheinhardt
A buffer whose size is not a multiple of four has been initialized using consecutive writes of 32bits. This results in a stack-buffer-overflow reported by ASAN in the checkasm-sw_scale FATE-test. Signed-off-by: Andreas Rheinhardt --- Instead of using FFALIGN one could also just remove the "- 1"