From: kernel test robot <lkp@intel.com>
To: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com>,
dri-devel@lists.freedesktop.org, christian.koenig@amd.com,
tursulin@igalia.com, simona.vetter@ffwll.ch, robdclark@gmail.com
Cc: oe-kbuild-all@lists.linux.dev,
Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com>
Subject: Re: [PATCH 1/3] drm: add DRM_SET_NAME ioctl
Date: Sat, 14 Sep 2024 07:06:21 +0800 [thread overview]
Message-ID: <202409140642.ZDKf0cja-lkp@intel.com> (raw)
In-Reply-To: <20240911145836.734080-1-pierre-eric.pelloux-prayer@amd.com>
Hi Pierre-Eric,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm-exynos/exynos-drm-next]
[also build test WARNING on drm-intel/for-linux-next drm-intel/for-linux-next-fixes drm-misc/drm-misc-next drm-tip/drm-tip linus/master v6.11-rc7 next-20240913]
[cannot apply to drm/drm-next]
[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/Pierre-Eric-Pelloux-Prayer/drm-use-drm_file-name-in-fdinfo/20240911-230058
base: https://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git exynos-drm-next
patch link: https://lore.kernel.org/r/20240911145836.734080-1-pierre-eric.pelloux-prayer%40amd.com
patch subject: [PATCH 1/3] drm: add DRM_SET_NAME ioctl
config: x86_64-randconfig-121-20240913 (https://download.01.org/0day-ci/archive/20240914/202409140642.ZDKf0cja-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240914/202409140642.ZDKf0cja-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/202409140642.ZDKf0cja-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/drm_ioctl.c:553:18: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected void *user_ptr @@ got void [noderef] __user * @@
drivers/gpu/drm/drm_ioctl.c:553:18: sparse: expected void *user_ptr
drivers/gpu/drm/drm_ioctl.c:553:18: sparse: got void [noderef] __user *
>> drivers/gpu/drm/drm_ioctl.c:555:36: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void const [noderef] __user * @@ got void *user_ptr @@
drivers/gpu/drm/drm_ioctl.c:555:36: sparse: expected void const [noderef] __user *
drivers/gpu/drm/drm_ioctl.c:555:36: sparse: got void *user_ptr
vim +553 drivers/gpu/drm/drm_ioctl.c
542
543 static int drm_set_name(struct drm_device *dev, void *data,
544 struct drm_file *file_priv)
545 {
546 struct drm_set_name *name = data;
547 void *user_ptr;
548 char *new_name;
549
550 if (name->name_len >= NAME_MAX)
551 return -EINVAL;
552
> 553 user_ptr = u64_to_user_ptr(name->name);
554
> 555 new_name = memdup_user_nul(user_ptr, name->name_len);
556
557 if (IS_ERR(new_name))
558 return PTR_ERR(new_name);
559
560 mutex_lock(&file_priv->name_lock);
561 if (file_priv->name)
562 kvfree(file_priv->name);
563 file_priv->name = new_name;
564 mutex_unlock(&file_priv->name_lock);
565
566 return 0;
567 }
568
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2024-09-13 23:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 14:58 [PATCH 1/3] drm: add DRM_SET_NAME ioctl Pierre-Eric Pelloux-Prayer
2024-09-11 14:58 ` [PATCH 2/3] drm: use drm_file name in fdinfo Pierre-Eric Pelloux-Prayer
2024-09-11 14:58 ` [PATCH 3/3] drm/amdgpu: use drm_file name Pierre-Eric Pelloux-Prayer
2024-09-12 8:24 ` Tvrtko Ursulin
2024-09-13 12:24 ` Pierre-Eric Pelloux-Prayer
2024-09-12 22:04 ` kernel test robot
2024-09-12 8:13 ` [PATCH 1/3] drm: add DRM_SET_NAME ioctl Tvrtko Ursulin
2024-09-13 12:17 ` Pierre-Eric Pelloux-Prayer
2024-09-13 12:21 ` Christian König
2024-09-13 13:44 ` Tvrtko Ursulin
2024-09-13 23:06 ` 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=202409140642.ZDKf0cja-lkp@intel.com \
--to=lkp@intel.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pierre-eric.pelloux-prayer@amd.com \
--cc=robdclark@gmail.com \
--cc=simona.vetter@ffwll.ch \
--cc=tursulin@igalia.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.