From: kernel test robot <lkp@intel.com>
To: Thomas Zimmermann <tzimmermann@suse.de>,
javierm@redhat.com, airlied@gmail.com, simona@ffwll.ch,
linux@armlinux.org.uk, maarten.lankhorst@linux.intel.com,
mripard@kernel.org, inki.dae@samsung.com, sw0312.kim@samsung.com,
kyungmin.park@samsung.com, patrik.r.jakobsson@gmail.com,
jani.nikula@linux.intel.com, rodrigo.vivi@intel.com,
robin.clark@oss.qualcomm.com, lumag@kernel.org,
abhinav.kumar@linux.dev, sean@poorly.run,
marijn.suijten@somainline.org, tomi.valkeinen@ideasonboard.com,
alexander.deucher@amd.com, christian.koenig@amd.com,
thierry.reding@gmail.com, mperttunen@nvidia.com,
jonathanh@nvidia.com
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
intel-xe@lists.freedesktop.org, linux-arm-msm@vger.kernel.org,
freedreno@lists.freedesktop.org, amd-gfx@lists.freedesktop.org,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH] drm/fb-helper: Allocate and release fb_info in single place
Date: Mon, 27 Oct 2025 08:46:39 +0800 [thread overview]
Message-ID: <202510270856.L1iU6js4-lkp@intel.com> (raw)
In-Reply-To: <20251026173944.219373-1-tzimmermann@suse.de>
Hi Thomas,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm-exynos/exynos-drm-next]
[also build test WARNING on drm-i915/for-linux-next drm-i915/for-linux-next-fixes tegra/for-next linus/master v6.18-rc2 next-20251024]
[cannot apply to rmk-arm/drm-armada-devel rmk-arm/drm-armada-fixes]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Thomas-Zimmermann/drm-fb-helper-Allocate-and-release-fb_info-in-single-place/20251027-014054
base: https://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git exynos-drm-next
patch link: https://lore.kernel.org/r/20251026173944.219373-1-tzimmermann%40suse.de
patch subject: [PATCH] drm/fb-helper: Allocate and release fb_info in single place
config: arm-randconfig-002-20251027 (https://download.01.org/0day-ci/archive/20251027/202510270856.L1iU6js4-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project e1ae12640102fd2b05bc567243580f90acb1135f)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251027/202510270856.L1iU6js4-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202510270856.L1iU6js4-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/drm_fbdev_ttm.c:208:26: warning: variable 'info' is uninitialized when used here [-Wuninitialized]
208 | drm_fb_helper_fill_info(info, fb_helper, sizes);
| ^~~~
drivers/gpu/drm/drm_fbdev_ttm.c:180:22: note: initialize the variable 'info' to silence this warning
180 | struct fb_info *info;
| ^
| = NULL
1 warning generated.
--
>> drivers/gpu/drm/armada/armada_fbdev.c:111:2: warning: unused label 'err_fballoc' [-Wunused-label]
111 | err_fballoc:
| ^~~~~~~~~~~~
1 warning generated.
--
>> drivers/gpu/drm/radeon/radeon_fbdev.c:275:1: warning: unused label 'err_drm_framebuffer_unregister_private' [-Wunused-label]
275 | err_drm_framebuffer_unregister_private:
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 warning generated.
vim +/info +208 drivers/gpu/drm/drm_fbdev_ttm.c
8ab59da26bc0ae drivers/gpu/drm/drm_fbdev_generic.c Thomas Zimmermann 2022-11-03 169
c7c1b9e1d52b0a drivers/gpu/drm/drm_fbdev_ttm.c Thomas Zimmermann 2024-09-24 170 /*
c7c1b9e1d52b0a drivers/gpu/drm/drm_fbdev_ttm.c Thomas Zimmermann 2024-09-24 171 * struct drm_driver
c7c1b9e1d52b0a drivers/gpu/drm/drm_fbdev_ttm.c Thomas Zimmermann 2024-09-24 172 */
c7c1b9e1d52b0a drivers/gpu/drm/drm_fbdev_ttm.c Thomas Zimmermann 2024-09-24 173
c7c1b9e1d52b0a drivers/gpu/drm/drm_fbdev_ttm.c Thomas Zimmermann 2024-09-24 174 int drm_fbdev_ttm_driver_fbdev_probe(struct drm_fb_helper *fb_helper,
c7c1b9e1d52b0a drivers/gpu/drm/drm_fbdev_ttm.c Thomas Zimmermann 2024-09-24 175 struct drm_fb_helper_surface_size *sizes)
c7c1b9e1d52b0a drivers/gpu/drm/drm_fbdev_ttm.c Thomas Zimmermann 2024-09-24 176 {
c7c1b9e1d52b0a drivers/gpu/drm/drm_fbdev_ttm.c Thomas Zimmermann 2024-09-24 177 struct drm_client_dev *client = &fb_helper->client;
c7c1b9e1d52b0a drivers/gpu/drm/drm_fbdev_ttm.c Thomas Zimmermann 2024-09-24 178 struct drm_device *dev = fb_helper->dev;
c7c1b9e1d52b0a drivers/gpu/drm/drm_fbdev_ttm.c Thomas Zimmermann 2024-09-24 179 struct drm_client_buffer *buffer;
c7c1b9e1d52b0a drivers/gpu/drm/drm_fbdev_ttm.c Thomas Zimmermann 2024-09-24 180 struct fb_info *info;
c7c1b9e1d52b0a drivers/gpu/drm/drm_fbdev_ttm.c Thomas Zimmermann 2024-09-24 181 size_t screen_size;
c7c1b9e1d52b0a drivers/gpu/drm/drm_fbdev_ttm.c Thomas Zimmermann 2024-09-24 182 void *screen_buffer;
c7c1b9e1d52b0a drivers/gpu/drm/drm_fbdev_ttm.c Thomas Zimmermann 2024-09-24 183 u32 format;
c7c1b9e1d52b0a drivers/gpu/drm/drm_fbdev_ttm.c Thomas Zimmermann 2024-09-24 184 int ret;
c7c1b9e1d52b0a drivers/gpu/drm/drm_fbdev_ttm.c Thomas Zimmermann 2024-09-24 185
c7c1b9e1d52b0a drivers/gpu/drm/drm_fbdev_ttm.c Thomas Zimmermann 2024-09-24 186 drm_dbg_kms(dev, "surface width(%d), height(%d) and bpp(%d)\n",
c7c1b9e1d52b0a drivers/gpu/drm/drm_fbdev_ttm.c Thomas Zimmermann 2024-09-24 187 sizes->surface_width, sizes->surface_height,
c7c1b9e1d52b0a drivers/gpu/drm/drm_fbdev_ttm.c Thomas Zimmermann 2024-09-24 188 sizes->surface_bpp);
c7c1b9e1d52b0a drivers/gpu/drm/drm_fbdev_ttm.c Thomas Zimmermann 2024-09-24 189
c7c1b9e1d52b0a drivers/gpu/drm/drm_fbdev_ttm.c Thomas Zimmermann 2024-09-24 190 format = drm_driver_legacy_fb_format(dev, sizes->surface_bpp,
c7c1b9e1d52b0a drivers/gpu/drm/drm_fbdev_ttm.c Thomas Zimmermann 2024-09-24 191 sizes->surface_depth);
c7c1b9e1d52b0a drivers/gpu/drm/drm_fbdev_ttm.c Thomas Zimmermann 2024-09-24 192 buffer = drm_client_framebuffer_create(client, sizes->surface_width,
c7c1b9e1d52b0a drivers/gpu/drm/drm_fbdev_ttm.c Thomas Zimmermann 2024-09-24 193 sizes->surface_height, format);
c7c1b9e1d52b0a drivers/gpu/drm/drm_fbdev_ttm.c Thomas Zimmermann 2024-09-24 194 if (IS_ERR(buffer))
c7c1b9e1d52b0a drivers/gpu/drm/drm_fbdev_ttm.c Thomas Zimmermann 2024-09-24 195 return PTR_ERR(buffer);
c7c1b9e1d52b0a drivers/gpu/drm/drm_fbdev_ttm.c Thomas Zimmermann 2024-09-24 196
c7c1b9e1d52b0a drivers/gpu/drm/drm_fbdev_ttm.c Thomas Zimmermann 2024-09-24 197 fb_helper->funcs = &drm_fbdev_ttm_helper_funcs;
c7c1b9e1d52b0a drivers/gpu/drm/drm_fbdev_ttm.c Thomas Zimmermann 2024-09-24 198 fb_helper->buffer = buffer;
c7c1b9e1d52b0a drivers/gpu/drm/drm_fbdev_ttm.c Thomas Zimmermann 2024-09-24 199 fb_helper->fb = buffer->fb;
c7c1b9e1d52b0a drivers/gpu/drm/drm_fbdev_ttm.c Thomas Zimmermann 2024-09-24 200
c7c1b9e1d52b0a drivers/gpu/drm/drm_fbdev_ttm.c Thomas Zimmermann 2024-09-24 201 screen_size = buffer->gem->size;
c7c1b9e1d52b0a drivers/gpu/drm/drm_fbdev_ttm.c Thomas Zimmermann 2024-09-24 202 screen_buffer = vzalloc(screen_size);
c7c1b9e1d52b0a drivers/gpu/drm/drm_fbdev_ttm.c Thomas Zimmermann 2024-09-24 203 if (!screen_buffer) {
c7c1b9e1d52b0a drivers/gpu/drm/drm_fbdev_ttm.c Thomas Zimmermann 2024-09-24 204 ret = -ENOMEM;
c7c1b9e1d52b0a drivers/gpu/drm/drm_fbdev_ttm.c Thomas Zimmermann 2024-09-24 205 goto err_drm_client_framebuffer_delete;
c7c1b9e1d52b0a drivers/gpu/drm/drm_fbdev_ttm.c Thomas Zimmermann 2024-09-24 206 }
c7c1b9e1d52b0a drivers/gpu/drm/drm_fbdev_ttm.c Thomas Zimmermann 2024-09-24 207
c7c1b9e1d52b0a drivers/gpu/drm/drm_fbdev_ttm.c Thomas Zimmermann 2024-09-24 @208 drm_fb_helper_fill_info(info, fb_helper, sizes);
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-10-27 0:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-26 17:18 [PATCH] drm/fb-helper: Allocate and release fb_info in single place Thomas Zimmermann
2025-10-26 19:24 ` ✓ i915.CI.BAT: success for " Patchwork
2025-10-26 22:21 ` ✗ i915.CI.Full: failure " Patchwork
2025-10-26 23:41 ` [PATCH] " kernel test robot
2025-10-27 0:46 ` kernel test robot [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202510270856.L1iU6js4-lkp@intel.com \
--to=lkp@intel.com \
--cc=abhinav.kumar@linux.dev \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=inki.dae@samsung.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=javierm@redhat.com \
--cc=jonathanh@nvidia.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=llvm@lists.linux.dev \
--cc=lumag@kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=marijn.suijten@somainline.org \
--cc=mperttunen@nvidia.com \
--cc=mripard@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=patrik.r.jakobsson@gmail.com \
--cc=robin.clark@oss.qualcomm.com \
--cc=rodrigo.vivi@intel.com \
--cc=sean@poorly.run \
--cc=simona@ffwll.ch \
--cc=sw0312.kim@samsung.com \
--cc=thierry.reding@gmail.com \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=tzimmermann@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).