All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Christian König" <ckoenig.leichtzumerken@gmail.com>,
	akpm@linux-foundation.org
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org,
	linux-mm@kvack.org, linux-media@vger.kernel.org
Subject: Re: [PATCH 2/2] mm: introduce vma_set_file function
Date: Tue, 15 Sep 2020 17:19:35 +0800	[thread overview]
Message-ID: <202009151711.gckf7JLJ%lkp@intel.com> (raw)
In-Reply-To: <20200914132920.59183-3-christian.koenig@amd.com>

[-- Attachment #1: Type: text/plain, Size: 3750 bytes --]

Hi "Christian,

I love your patch! Yet something to improve:

[auto build test ERROR on hnaz-linux-mm/master]
[also build test ERROR on drm-intel/for-linux-next drm-tip/drm-tip linus/master v5.9-rc5 next-20200914]
[cannot apply to tegra-drm/drm/tegra/for-next drm-exynos/exynos-drm-next 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]

url:    https://github.com/0day-ci/linux/commits/Christian-K-nig/drm-shmem-helpers-revert-Redirect-mmap-for-imported-dma-buf/20200914-222921
base:   https://github.com/hnaz/linux-mm master
config: h8300-randconfig-r023-20200914 (attached as .config)
compiler: h8300-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=h8300 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   h8300-linux-ld: drivers/dma-buf/dma-buf.o: in function `dma_buf_mmap':
>> drivers/dma-buf/dma-buf.c:1166: undefined reference to `vma_set_file'
>> h8300-linux-ld: drivers/dma-buf/dma-buf.c:1172: undefined reference to `vma_set_file'
   h8300-linux-ld: drivers/leds/leds-lp55xx-common.o: in function `devm_led_classdev_register':
   include/linux/leds.h:200: undefined reference to `devm_led_classdev_register_ext'

# https://github.com/0day-ci/linux/commit/c558278651bbea7cb67487890a983608764cc7f4
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Christian-K-nig/drm-shmem-helpers-revert-Redirect-mmap-for-imported-dma-buf/20200914-222921
git checkout c558278651bbea7cb67487890a983608764cc7f4
vim +1166 drivers/dma-buf/dma-buf.c

  1127	
  1128	
  1129	/**
  1130	 * dma_buf_mmap - Setup up a userspace mmap with the given vma
  1131	 * @dmabuf:	[in]	buffer that should back the vma
  1132	 * @vma:	[in]	vma for the mmap
  1133	 * @pgoff:	[in]	offset in pages where this mmap should start within the
  1134	 *			dma-buf buffer.
  1135	 *
  1136	 * This function adjusts the passed in vma so that it points at the file of the
  1137	 * dma_buf operation. It also adjusts the starting pgoff and does bounds
  1138	 * checking on the size of the vma. Then it calls the exporters mmap function to
  1139	 * set up the mapping.
  1140	 *
  1141	 * Can return negative error values, returns 0 on success.
  1142	 */
  1143	int dma_buf_mmap(struct dma_buf *dmabuf, struct vm_area_struct *vma,
  1144			 unsigned long pgoff)
  1145	{
  1146		struct file *oldfile;
  1147		int ret;
  1148	
  1149		if (WARN_ON(!dmabuf || !vma))
  1150			return -EINVAL;
  1151	
  1152		/* check if buffer supports mmap */
  1153		if (!dmabuf->ops->mmap)
  1154			return -EINVAL;
  1155	
  1156		/* check for offset overflow */
  1157		if (pgoff + vma_pages(vma) < pgoff)
  1158			return -EOVERFLOW;
  1159	
  1160		/* check for overflowing the buffer's size */
  1161		if (pgoff + vma_pages(vma) >
  1162		    dmabuf->size >> PAGE_SHIFT)
  1163			return -EINVAL;
  1164	
  1165		/* readjust the vma */
> 1166		oldfile = vma_set_file(vma, dmabuf->file);
  1167		vma->vm_pgoff = pgoff;
  1168	
  1169		ret = dmabuf->ops->mmap(dmabuf, vma);
  1170		/* restore old parameters on failure */
  1171		if (ret)
> 1172			vma_set_file(vma, oldfile);
  1173	
  1174		return ret;
  1175	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 17778 bytes --]

[-- Attachment #3: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH 2/2] mm: introduce vma_set_file function
Date: Tue, 15 Sep 2020 17:19:35 +0800	[thread overview]
Message-ID: <202009151711.gckf7JLJ%lkp@intel.com> (raw)
In-Reply-To: <20200914132920.59183-3-christian.koenig@amd.com>

[-- Attachment #1: Type: text/plain, Size: 3843 bytes --]

Hi "Christian,

I love your patch! Yet something to improve:

[auto build test ERROR on hnaz-linux-mm/master]
[also build test ERROR on drm-intel/for-linux-next drm-tip/drm-tip linus/master v5.9-rc5 next-20200914]
[cannot apply to tegra-drm/drm/tegra/for-next drm-exynos/exynos-drm-next 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]

url:    https://github.com/0day-ci/linux/commits/Christian-K-nig/drm-shmem-helpers-revert-Redirect-mmap-for-imported-dma-buf/20200914-222921
base:   https://github.com/hnaz/linux-mm master
config: h8300-randconfig-r023-20200914 (attached as .config)
compiler: h8300-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=h8300 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   h8300-linux-ld: drivers/dma-buf/dma-buf.o: in function `dma_buf_mmap':
>> drivers/dma-buf/dma-buf.c:1166: undefined reference to `vma_set_file'
>> h8300-linux-ld: drivers/dma-buf/dma-buf.c:1172: undefined reference to `vma_set_file'
   h8300-linux-ld: drivers/leds/leds-lp55xx-common.o: in function `devm_led_classdev_register':
   include/linux/leds.h:200: undefined reference to `devm_led_classdev_register_ext'

# https://github.com/0day-ci/linux/commit/c558278651bbea7cb67487890a983608764cc7f4
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Christian-K-nig/drm-shmem-helpers-revert-Redirect-mmap-for-imported-dma-buf/20200914-222921
git checkout c558278651bbea7cb67487890a983608764cc7f4
vim +1166 drivers/dma-buf/dma-buf.c

  1127	
  1128	
  1129	/**
  1130	 * dma_buf_mmap - Setup up a userspace mmap with the given vma
  1131	 * @dmabuf:	[in]	buffer that should back the vma
  1132	 * @vma:	[in]	vma for the mmap
  1133	 * @pgoff:	[in]	offset in pages where this mmap should start within the
  1134	 *			dma-buf buffer.
  1135	 *
  1136	 * This function adjusts the passed in vma so that it points at the file of the
  1137	 * dma_buf operation. It also adjusts the starting pgoff and does bounds
  1138	 * checking on the size of the vma. Then it calls the exporters mmap function to
  1139	 * set up the mapping.
  1140	 *
  1141	 * Can return negative error values, returns 0 on success.
  1142	 */
  1143	int dma_buf_mmap(struct dma_buf *dmabuf, struct vm_area_struct *vma,
  1144			 unsigned long pgoff)
  1145	{
  1146		struct file *oldfile;
  1147		int ret;
  1148	
  1149		if (WARN_ON(!dmabuf || !vma))
  1150			return -EINVAL;
  1151	
  1152		/* check if buffer supports mmap */
  1153		if (!dmabuf->ops->mmap)
  1154			return -EINVAL;
  1155	
  1156		/* check for offset overflow */
  1157		if (pgoff + vma_pages(vma) < pgoff)
  1158			return -EOVERFLOW;
  1159	
  1160		/* check for overflowing the buffer's size */
  1161		if (pgoff + vma_pages(vma) >
  1162		    dmabuf->size >> PAGE_SHIFT)
  1163			return -EINVAL;
  1164	
  1165		/* readjust the vma */
> 1166		oldfile = vma_set_file(vma, dmabuf->file);
  1167		vma->vm_pgoff = pgoff;
  1168	
  1169		ret = dmabuf->ops->mmap(dmabuf, vma);
  1170		/* restore old parameters on failure */
  1171		if (ret)
> 1172			vma_set_file(vma, oldfile);
  1173	
  1174		return ret;
  1175	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 17778 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: "Christian König" <ckoenig.leichtzumerken@gmail.com>,
	akpm@linux-foundation.org
Cc: kbuild-all@lists.01.org, sumit.semwal@linaro.org,
	linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
	linaro-mm-sig@lists.linaro.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: [PATCH 2/2] mm: introduce vma_set_file function
Date: Tue, 15 Sep 2020 17:19:35 +0800	[thread overview]
Message-ID: <202009151711.gckf7JLJ%lkp@intel.com> (raw)
In-Reply-To: <20200914132920.59183-3-christian.koenig@amd.com>

[-- Attachment #1: Type: text/plain, Size: 3750 bytes --]

Hi "Christian,

I love your patch! Yet something to improve:

[auto build test ERROR on hnaz-linux-mm/master]
[also build test ERROR on drm-intel/for-linux-next drm-tip/drm-tip linus/master v5.9-rc5 next-20200914]
[cannot apply to tegra-drm/drm/tegra/for-next drm-exynos/exynos-drm-next 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]

url:    https://github.com/0day-ci/linux/commits/Christian-K-nig/drm-shmem-helpers-revert-Redirect-mmap-for-imported-dma-buf/20200914-222921
base:   https://github.com/hnaz/linux-mm master
config: h8300-randconfig-r023-20200914 (attached as .config)
compiler: h8300-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=h8300 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   h8300-linux-ld: drivers/dma-buf/dma-buf.o: in function `dma_buf_mmap':
>> drivers/dma-buf/dma-buf.c:1166: undefined reference to `vma_set_file'
>> h8300-linux-ld: drivers/dma-buf/dma-buf.c:1172: undefined reference to `vma_set_file'
   h8300-linux-ld: drivers/leds/leds-lp55xx-common.o: in function `devm_led_classdev_register':
   include/linux/leds.h:200: undefined reference to `devm_led_classdev_register_ext'

# https://github.com/0day-ci/linux/commit/c558278651bbea7cb67487890a983608764cc7f4
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Christian-K-nig/drm-shmem-helpers-revert-Redirect-mmap-for-imported-dma-buf/20200914-222921
git checkout c558278651bbea7cb67487890a983608764cc7f4
vim +1166 drivers/dma-buf/dma-buf.c

  1127	
  1128	
  1129	/**
  1130	 * dma_buf_mmap - Setup up a userspace mmap with the given vma
  1131	 * @dmabuf:	[in]	buffer that should back the vma
  1132	 * @vma:	[in]	vma for the mmap
  1133	 * @pgoff:	[in]	offset in pages where this mmap should start within the
  1134	 *			dma-buf buffer.
  1135	 *
  1136	 * This function adjusts the passed in vma so that it points at the file of the
  1137	 * dma_buf operation. It also adjusts the starting pgoff and does bounds
  1138	 * checking on the size of the vma. Then it calls the exporters mmap function to
  1139	 * set up the mapping.
  1140	 *
  1141	 * Can return negative error values, returns 0 on success.
  1142	 */
  1143	int dma_buf_mmap(struct dma_buf *dmabuf, struct vm_area_struct *vma,
  1144			 unsigned long pgoff)
  1145	{
  1146		struct file *oldfile;
  1147		int ret;
  1148	
  1149		if (WARN_ON(!dmabuf || !vma))
  1150			return -EINVAL;
  1151	
  1152		/* check if buffer supports mmap */
  1153		if (!dmabuf->ops->mmap)
  1154			return -EINVAL;
  1155	
  1156		/* check for offset overflow */
  1157		if (pgoff + vma_pages(vma) < pgoff)
  1158			return -EOVERFLOW;
  1159	
  1160		/* check for overflowing the buffer's size */
  1161		if (pgoff + vma_pages(vma) >
  1162		    dmabuf->size >> PAGE_SHIFT)
  1163			return -EINVAL;
  1164	
  1165		/* readjust the vma */
> 1166		oldfile = vma_set_file(vma, dmabuf->file);
  1167		vma->vm_pgoff = pgoff;
  1168	
  1169		ret = dmabuf->ops->mmap(dmabuf, vma);
  1170		/* restore old parameters on failure */
  1171		if (ret)
> 1172			vma_set_file(vma, oldfile);
  1173	
  1174		return ret;
  1175	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 17778 bytes --]

  reply	other threads:[~2020-09-15  9:20 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-14 13:29 Changing vma->vm_file in dma_buf_mmap() Christian König
2020-09-14 13:29 ` Christian König
2020-09-14 13:29 ` [PATCH 1/2] drm/shmem-helpers: revert "Redirect mmap for imported dma-buf" Christian König
2020-09-14 13:29   ` Christian König
2020-09-15 10:39   ` Daniel Vetter
2020-09-15 10:39     ` Daniel Vetter
2020-09-15 11:03     ` Christian König
2020-09-15 11:03       ` Christian König
2020-09-15 11:07       ` Daniel Vetter
2020-09-15 11:07         ` Daniel Vetter
2020-09-14 13:29 ` [PATCH 2/2] mm: introduce vma_set_file function Christian König
2020-09-14 13:29   ` Christian König
2020-09-15  9:19   ` kernel test robot [this message]
2020-09-15  9:19     ` kernel test robot
2020-09-15  9:19     ` kernel test robot
2020-09-15 11:57   ` kernel test robot
2020-09-15 11:57     ` kernel test robot
2020-09-15 11:57     ` kernel test robot
2020-09-14 13:30 ` Changing vma->vm_file in dma_buf_mmap() Christian König
2020-09-14 13:30   ` Christian König
2020-09-14 14:06   ` Jason Gunthorpe
2020-09-14 14:06     ` Jason Gunthorpe
2020-09-14 18:26     ` Christian König
2020-09-14 18:26       ` Christian König
2020-09-16  9:53       ` Daniel Vetter
2020-09-16  9:53         ` Daniel Vetter
2020-09-16 10:14         ` Christian König
2020-09-16 10:14           ` Christian König
2020-09-16 11:45           ` Christian König
2020-09-16 11:45             ` Christian König
2020-09-16 12:41             ` Daniel Vetter
2020-09-16 12:41               ` Daniel Vetter
2020-09-16 14:07         ` Jason Gunthorpe
2020-09-16 14:07           ` Jason Gunthorpe
2020-09-16 14:14           ` Christian König
2020-09-16 14:14             ` Christian König
2020-09-16 15:24             ` Daniel Vetter
2020-09-16 15:24               ` Daniel Vetter
2020-09-16 15:31               ` [Linaro-mm-sig] " Christian König
2020-09-16 15:31                 ` Christian König
2020-09-17  6:23                 ` Daniel Vetter
2020-09-17  6:23                   ` Daniel Vetter
2020-09-17  7:11                   ` Christian König
2020-09-17  7:11                     ` Christian König
2020-09-17  8:09                     ` Daniel Vetter
2020-09-17  8:09                       ` Daniel Vetter
2020-09-17 11:31                       ` Jason Gunthorpe
2020-09-17 11:31                         ` Jason Gunthorpe
2020-09-17 12:03                         ` Christian König
2020-09-17 12:03                           ` Christian König
2020-09-17 12:18                           ` Jason Gunthorpe
2020-09-17 12:18                             ` Jason Gunthorpe
2020-09-17 12:24                             ` Christian König
2020-09-17 12:24                               ` Christian König
2020-09-17 12:26                               ` Daniel Vetter
2020-09-17 12:26                                 ` Daniel Vetter
2020-09-17 14:35                               ` Jason Gunthorpe
2020-09-17 14:35                                 ` Jason Gunthorpe
2020-09-17 14:54                                 ` Christian König
2020-09-17 14:54                                   ` Christian König
2020-09-17 15:24                                   ` Jason Gunthorpe
2020-09-17 15:24                                     ` Jason Gunthorpe
2020-09-17 15:37                                     ` Daniel Vetter
2020-09-17 15:37                                       ` Daniel Vetter
2020-09-17 16:06                                       ` Christian König
2020-09-17 16:06                                         ` Christian König
2020-09-17 16:39                                         ` Jason Gunthorpe
2020-09-17 16:39                                           ` Jason Gunthorpe
2020-09-17 17:23                                           ` Daniel Vetter
2020-09-17 17:23                                             ` Daniel Vetter

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=202009151711.gckf7JLJ%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=ckoenig.leichtzumerken@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linaro-mm-sig@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    /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.