Re: [Nouveau] [PATCH] drm/nouveau/disp: Fix nvif_outp_acquire_dp() argument size

2023-02-09 Thread Lyude Paul
I think that shoud be fine, which branch is it on? On Fri, 2023-01-27 at 11:42 -0800, Kees Cook wrote: > On Wed, Jan 25, 2023 at 04:24:19PM -0500, Lyude Paul wrote: > > Sorry! I've been pretty busy until now, this is: > > > > Reviewed-by: Lyude Paul > > > > Let me know if you've pushed it

Re: [Nouveau] [PATCH] drm/nouveau/disp: Fix nvif_outp_acquire_dp() argument size

2023-01-27 Thread Kees Cook
On Wed, Jan 25, 2023 at 04:24:19PM -0500, Lyude Paul wrote: > Sorry! I've been pretty busy until now, this is: > > Reviewed-by: Lyude Paul > > Let me know if you've pushed it already or if you want me to push it to drm- > misc Either way is fine. I'm currently carrying it, but I can easily

Re: [Nouveau] [PATCH] drm/nouveau/disp: Fix nvif_outp_acquire_dp() argument size

2023-01-25 Thread Lyude Paul
Sorry! I've been pretty busy until now, this is: Reviewed-by: Lyude Paul Let me know if you've pushed it already or if you want me to push it to drm- misc On Wed, 2023-01-25 at 12:15 -0800, Kees Cook wrote: > Ping. I'll take this via my tree unless someone else wants to take it... > > On Sun,

Re: [Nouveau] [PATCH] drm/nouveau/disp: Fix nvif_outp_acquire_dp() argument size

2023-01-25 Thread Kees Cook
Ping. I'll take this via my tree unless someone else wants to take it... On Sun, Nov 27, 2022 at 10:30:41AM -0800, Kees Cook wrote: > Both Coverity and GCC with -Wstringop-overflow noticed that > nvif_outp_acquire_dp() accidentally defined its second argument with 1 > additional element: > >