[drm-misc:drm-misc-next 7/10] arch/powerpc/include/asm/page.h:25:33: error: conversion from 'long unsigned int' to 'u16' {aka 'short unsigned int'} changes value from '65536' to '0'

2024-05-18 Thread kernel test robot
tree: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next head: 85cb9d603953d77de5cb311d229a79c439ff6bfb commit: dc6fcaaba5a5411237d042a26c4d46689f3346bb [7/10] drm/omap: Allow build with COMPILE_TEST=y config: powerpc-allmodconfig

[drm-misc:topic/rust-drm 13/16] warning: trait `Sealed` is never used

2024-05-18 Thread kernel test robot
tree: git://anongit.freedesktop.org/drm/drm-misc topic/rust-drm head: 440a8db3f583392a1a894f32782ecc397911f9af commit: a92c0d93ee103b33d566d4e6ba88e3dc691db856 [13/16] rust: Add a Sealed trait config: x86_64-rhel-8.3-rust

Re: [PATCH] drm/nouveau/nvif: Avoid build error due to potential integer overflows

2024-05-18 Thread Joe Perches
On Sat, 2024-05-18 at 11:23 -0700, Guenter Roeck wrote: > On 5/18/24 10:32, Kees Cook wrote: > [] > > I think the INT_MAX test is actually better in this case because > > nvif_object_ioctl()'s size argument is u32: > > > > ret = nvif_object_ioctl(object, args, sizeof(*args) + size, NULL); > >

Re: Kernel 5.15.150 black screen with AMD Raven/Picasso GPU

2024-05-18 Thread Armin Wolf
Am 17.05.24 um 03:30 schrieb Barry Kauler: Armin, Yifan, Prike, I will top-post, so you don't have to scroll down. After identifying the commit that causes black screen with my gpu, I posted the result to you guys, on May 9. It is now May 17 and no reply. OK, I have now created a patch that

[drm-misc:drm-misc-next 10/10] drivers/gpu/drm/stm/ltdc.c:494:35: error: unused function 'encoder_to_ltdc'

2024-05-18 Thread kernel test robot
Hi Ville, First bad commit (maybe != root cause): tree: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next head: 85cb9d603953d77de5cb311d229a79c439ff6bfb commit: 6597efcfc53585d5fb177b901a41b4ac2f282b99 [10/10] drm/stm: Allow build with COMPILE_TEST=y config: x86_64-allyesconfig

Re: [PATCH v2] drm/nouveau/nvif: Avoid build error due to potential integer overflows

2024-05-18 Thread Kees Cook
On Sat, May 18, 2024 at 11:29:23AM -0700, Guenter Roeck wrote: > Trying to build parisc:allmodconfig with gcc 12.x or later results > in the following build error. > > drivers/gpu/drm/nouveau/nvif/object.c: In function 'nvif_object_mthd': > drivers/gpu/drm/nouveau/nvif/object.c:161:9: error: >

Re: [PATCH net-next v9 04/14] netdev: support binding dma-buf to netdevice

2024-05-18 Thread David Wei
On 2024-05-10 16:21, Mina Almasry wrote: > -/* Stub */ > int netdev_nl_bind_rx_doit(struct sk_buff *skb, struct genl_info *info) > { > - return 0; > + struct nlattr *tb[ARRAY_SIZE(netdev_queue_dmabuf_nl_policy)]; > + struct net_devmem_dmabuf_binding *out_binding; > + struct

Re: [PATCH net-next v9 04/14] netdev: support binding dma-buf to netdevice

2024-05-18 Thread David Wei
On 2024-05-10 16:21, Mina Almasry wrote: > +void net_devmem_unbind_dmabuf(struct net_devmem_dmabuf_binding *binding) > +{ > + struct netdev_rx_queue *rxq; > + unsigned long xa_idx; > + unsigned int rxq_idx; > + > + if (!binding) > + return; > + > + if

[PATCH v2] drm/nouveau/nvif: Avoid build error due to potential integer overflows

2024-05-18 Thread Guenter Roeck
Trying to build parisc:allmodconfig with gcc 12.x or later results in the following build error. drivers/gpu/drm/nouveau/nvif/object.c: In function 'nvif_object_mthd': drivers/gpu/drm/nouveau/nvif/object.c:161:9: error: 'memcpy' accessing 4294967264 or more bytes at offsets 0 and 32

Re: [PATCH] drm/nouveau/nvif: Avoid build error due to potential integer overflows

2024-05-18 Thread Guenter Roeck
On 5/18/24 10:32, Kees Cook wrote: On Sat, May 18, 2024 at 06:54:36PM +0200, Christophe JAILLET wrote: (adding linux-harden...@vger.kernel.org) Le 18/05/2024 à 16:37, Guenter Roeck a écrit : Trying to build parisc:allmodconfig with gcc 12.x or later results in the following build error.

Re: [PATCH] dma-buf/fence-array: Add flex array to struct dma_fence_array

2024-05-18 Thread Kees Cook
On Sat, May 18, 2024 at 07:47:02PM +0200, Christophe JAILLET wrote: > This is an effort to get rid of all multiplications from allocation > functions in order to prevent integer overflows [1][2]. > > The "struct dma_fence_array" can be refactored to add a flex array in order > to have the

[PATCH] dma-buf/fence-array: Add flex array to struct dma_fence_array

2024-05-18 Thread Christophe JAILLET
This is an effort to get rid of all multiplications from allocation functions in order to prevent integer overflows [1][2]. The "struct dma_fence_array" can be refactored to add a flex array in order to have the "callback structures allocated behind the array" be more explicit. Do so: - makes

Re: [PATCH] drm/nouveau/nvif: Avoid build error due to potential integer overflows

2024-05-18 Thread Kees Cook
On Sat, May 18, 2024 at 06:54:36PM +0200, Christophe JAILLET wrote: > (adding linux-harden...@vger.kernel.org) > > > Le 18/05/2024 à 16:37, Guenter Roeck a écrit : > > Trying to build parisc:allmodconfig with gcc 12.x or later results > > in the following build error. > > > >

Re: [PATCH] drm/nouveau/nvif: Avoid build error due to potential integer overflows

2024-05-18 Thread Christophe JAILLET
(adding linux-harden...@vger.kernel.org) Le 18/05/2024 à 16:37, Guenter Roeck a écrit : Trying to build parisc:allmodconfig with gcc 12.x or later results in the following build error. drivers/gpu/drm/nouveau/nvif/object.c: In function 'nvif_object_mthd':

[PATCH] drm/nouveau/nvif: Avoid build error due to potential integer overflows

2024-05-18 Thread Guenter Roeck
Trying to build parisc:allmodconfig with gcc 12.x or later results in the following build error. drivers/gpu/drm/nouveau/nvif/object.c: In function 'nvif_object_mthd': drivers/gpu/drm/nouveau/nvif/object.c:161:9: error: 'memcpy' accessing 4294967264 or more bytes at offsets 0 and 32

Re: [PATCH v5 5/8] drm/xe: Add helper to accumulate exec queue runtime

2024-05-18 Thread Lucas De Marchi
On Fri, May 17, 2024 at 03:40:22PM GMT, Matt Roper wrote: On Fri, May 17, 2024 at 01:43:07PM -0700, Lucas De Marchi wrote: From: Umesh Nerlige Ramappa Add a helper to accumulate per-client runtime of all its exec queues. This is called every time a sched job is finished. v2: - Use

Re: [RFT,v2,26/48] drm/panel: simple: Stop tracking prepared/enabled

2024-05-18 Thread Sui Jingfeng
Hi, On 2024/5/4 05:33, Douglas Anderson wrote: As talked about in commit d2aacaf07395 ("drm/panel: Check for already prepared/enabled in drm_panel"), we want to remove needless code from panel drivers that was storing and double-checking the prepared/enabled state. Even if someone was relying

Re: [PATCH v2 1/4] drm/vmwgfx: Filter modes which exceed graphics memory

2024-05-18 Thread kernel test robot
-which-exceed-graphics-memory/20240518-024955 base: git://anongit.freedesktop.org/drm/drm drm-next patch link: https://lore.kernel.org/r/20240517184811.25807-2-ian.forbes%40broadcom.com patch subject: [PATCH v2 1/4] drm/vmwgfx: Filter modes which exceed graphics memory config: i386-randconfig-141

Re: [RESEND v7 00/37] Device Tree support for SH7751 based board

2024-05-18 Thread John Paul Adrian Glaubitz
Hi Yoshinori, On Thu, 2024-04-04 at 14:14 +0900, Yoshinori Sato wrote: > Sorry. previus mail is thread broken. > > This is an updated version of something I wrote about 7 years ago. > Minimum support for R2D-plus and LANDISK. > I think R2D-1 will work if you add AX88796 to dts. > And

DRM Accel BoF at Linux Plumbers

2024-05-18 Thread Tomeu Vizoso
Hi, I would like to use the chance at the next Plumbers to discuss the present challenges related to ML accelerators in mainline. I'm myself more oriented towards edge-oriented deployments, and don't know enough about how these accelerators are being used in the cloud (and maybe desktop?) to