From: kernel test robot <lkp@intel.com>
To: "Andi Shyti" <andi.shyti@linux.intel.com>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Christian König" <christian.koenig@amd.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
oe-kbuild-all@lists.linux.dev,
Chris Wilson <chris.p.wilson@linux.intel.com>,
linux-media@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH] dma-buf: Deny copy-on-writes mmaps
Date: Wed, 4 Oct 2023 11:54:10 +0800 [thread overview]
Message-ID: <202310041156.Bi2Vshvb-lkp@intel.com> (raw)
In-Reply-To: <20231003230332.513051-1-andi.shyti@linux.intel.com>
Hi Andi,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-misc/drm-misc-next]
[also build test ERROR on linus/master v6.6-rc4 next-20231003]
[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/Andi-Shyti/dma-buf-Deny-copy-on-writes-mmaps/20231004-070556
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link: https://lore.kernel.org/r/20231003230332.513051-1-andi.shyti%40linux.intel.com
patch subject: [PATCH] dma-buf: Deny copy-on-writes mmaps
config: sh-allyesconfig (https://download.01.org/0day-ci/archive/20231004/202310041156.Bi2Vshvb-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231004/202310041156.Bi2Vshvb-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/202310041156.Bi2Vshvb-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/dma-buf/dma-buf.c: In function 'dma_buf_get_unmapped_area':
>> drivers/dma-buf/dma-buf.c:142:27: error: 'struct mm_struct' has no member named 'get_unmapped_area'
142 | return current->mm->get_unmapped_area(file, addr, len, pgoff, flags);
| ^~
drivers/dma-buf/dma-buf.c:143:1: error: control reaches end of non-void function [-Werror=return-type]
143 | }
| ^
cc1: some warnings being treated as errors
vim +142 drivers/dma-buf/dma-buf.c
131
132 static unsigned long
133 dma_buf_get_unmapped_area(struct file *file,
134 unsigned long addr,
135 unsigned long len,
136 unsigned long pgoff,
137 unsigned long flags)
138 {
139 if ((flags & MAP_TYPE) == MAP_PRIVATE)
140 return -EINVAL;
141
> 142 return current->mm->get_unmapped_area(file, addr, len, pgoff, flags);
143 }
144
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-10-04 3:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 23:03 [Intel-gfx] [PATCH] dma-buf: Deny copy-on-writes mmaps Andi Shyti
2023-10-04 0:02 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2023-10-04 2:14 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-10-04 3:54 ` kernel test robot [this message]
2023-10-04 14:16 ` [Intel-gfx] [PATCH] " Christian König
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=202310041156.Bi2Vshvb-lkp@intel.com \
--to=lkp@intel.com \
--cc=andi.shyti@linux.intel.com \
--cc=chris.p.wilson@linux.intel.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-media@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sumit.semwal@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox