From: kernel test robot <lkp@intel.com>
To: Edward Wu <edwardwu@realtek.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
surenb@google.com, minchan@google.com, edwardwu@realtek.com
Subject: Re: [PATCH] mm: cma: sync everything after EBUSY
Date: Thu, 16 Jun 2022 03:34:46 +0800 [thread overview]
Message-ID: <202206160330.nZiFjZFG-lkp@intel.com> (raw)
In-Reply-To: <20220615021504.23358-1-edwardwu@realtek.com>
Hi Edward,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on akpm-mm/mm-everything]
url: https://github.com/intel-lab-lkp/linux/commits/Edward-Wu/mm-cma-sync-everything-after-EBUSY/20220615-101716
base: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
config: xtensa-allyesconfig (https://download.01.org/0day-ci/archive/20220616/202206160330.nZiFjZFG-lkp@intel.com/config)
compiler: xtensa-linux-gcc (GCC) 11.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
# https://github.com/intel-lab-lkp/linux/commit/ef04552ed13eb371365fcc55c7ae1e5c3c211168
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Edward-Wu/mm-cma-sync-everything-after-EBUSY/20220615-101716
git checkout ef04552ed13eb371365fcc55c7ae1e5c3c211168
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 make.cross W=1 O=build_dir ARCH=xtensa SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> mm/cma.c:415:6: warning: no previous prototype for 'cma_sync_work' [-Wmissing-prototypes]
415 | void cma_sync_work(struct work_struct *work)
| ^~~~~~~~~~~~~
>> mm/cma.c:422:6: warning: no previous prototype for 'cma_ebusy_sync_pinned_pages' [-Wmissing-prototypes]
422 | void cma_ebusy_sync_pinned_pages(void)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/cma_sync_work +415 mm/cma.c
414
> 415 void cma_sync_work(struct work_struct *work)
416 {
417 ksys_sync();
418 kfree(work);
419 pr_debug("%s(): EBUSY Sync complete\n", __func__);
420 }
421
> 422 void cma_ebusy_sync_pinned_pages(void)
423 {
424 struct work_struct *work;
425
426 work = kmalloc(sizeof(*work), GFP_ATOMIC);
427 if (work) {
428 INIT_WORK(work, cma_sync_work);
429 schedule_work(work);
430 }
431 }
432
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next prev parent reply other threads:[~2022-06-15 19:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 2:15 Edward Wu
2022-06-15 19:34 ` kernel test robot [this message]
2022-06-15 23:24 ` [PATCH v2] " Edward Wu
2022-06-15 23:34 ` [PATCH v3] " Edward Wu
2022-06-21 2:38 ` [PATCH] " kernel test robot
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=202206160330.nZiFjZFG-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=edwardwu@realtek.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@google.com \
--cc=surenb@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox