Hi Krzysztof, On Friday, 23 January 2026 11:11:30 CET Krzysztof Karas wrote: > It was observed that during fault injection testing the > vgpu.entry remains uninitialized when taking the error path, > which results in warnings [1]: > > <6> [491.828427] list_del corruption, ffff88812cd2d0c8->next is NULL > <4> [491.828430] WARNING: lib/list_debug.c:52 at > __list_del_entry_valid_or_report+0x6f/0x120, CPU#2: i915_module_loa/2921 > > Add initialization step to intel_vgpu_detect().
I do second Sebastian's comment on that. > > Signed-off-by: Krzysztof Karas <[email protected]> > --- > > Example of failure from intel-gfx-ci: > https://intel-gfx-ci.01.org/tree/drm-tip/IGT_8711/shard-dg2-5/igt@[email protected]#dmesg-warnings385 Is there an issue focused on that problem open on our Gitlab? If yes then I think it's better to provide a link it instead. The report you refer to may disappear soon. And, a stable link should be better added with a Link: or even Closes: tag instead of here. > > drivers/gpu/drm/i915/i915_vgpu.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/drivers/gpu/drm/i915/i915_vgpu.c > b/drivers/gpu/drm/i915/i915_vgpu.c > index d29a06ea51a5..362282b20f7b 100644 > --- a/drivers/gpu/drm/i915/i915_vgpu.c > +++ b/drivers/gpu/drm/i915/i915_vgpu.c > @@ -67,6 +67,7 @@ void intel_vgpu_detect(struct drm_i915_private *dev_priv) > u64 magic; > u16 version_major; > void __iomem *shared_area; > + INIT_LIST_HEAD(&dev_priv->vgpu.entry); In addition to what Sebastian already stated, please avoid placing executable statements in declaration sections. Thanks, Janusz > > BUILD_BUG_ON(sizeof(struct vgt_if) != VGT_PVINFO_SIZE); > >
