All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Lukas Hruska <lhruska@suse.cz>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH 2/4 v1] livedump: Add write protection management
Date: Sat, 11 Nov 2023 13:20:50 +0800	[thread overview]
Message-ID: <202311111350.ddmhyoBh-lkp@intel.com> (raw)
In-Reply-To: <20231110150057.15717-3-lhruska@suse.cz>

Hi Lukas,

[This is a private test report for your RFC patch.]
kernel test robot noticed the following build warnings:

[auto build test WARNING on tip/x86/core]
[also build test WARNING on tip/x86/mm linus/master v6.6 next-20231110]
[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/Lukas-Hruska/crash-vmcore-VMCOREINFO-creation-from-non-kdump-kernel/20231111-022332
base:   tip/x86/core
patch link:    https://lore.kernel.org/r/20231110150057.15717-3-lhruska%40suse.cz
patch subject: [RFC PATCH 2/4 v1] livedump: Add write protection management
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20231111/202311111350.ddmhyoBh-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231111/202311111350.ddmhyoBh-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/202311111350.ddmhyoBh-lkp@intel.com/

All warnings (new ones prefixed by >>):

   arch/x86/mm/wrprotect.c: In function 'split_large_pages':
>> arch/x86/mm/wrprotect.c:103:13: warning: variable 'ret' set but not used [-Wunused-but-set-variable]
     103 |         int ret;
         |             ^~~
   arch/x86/mm/wrprotect.c: In function 'handle_tasks':
   arch/x86/mm/wrprotect.c:263:9: error: implicit declaration of function 'do_each_thread'; did you mean 'for_each_thread'? [-Werror=implicit-function-declaration]
     263 |         do_each_thread(p, t) {
         |         ^~~~~~~~~~~~~~
         |         for_each_thread
   arch/x86/mm/wrprotect.c:263:29: error: expected ';' before '{' token
     263 |         do_each_thread(p, t) {
         |                             ^~
         |                             ;
   In file included from include/linux/pgtable.h:6,
                    from include/linux/mm.h:29,
                    from arch/x86/include/asm/wrprotect.h:23,
                    from arch/x86/mm/wrprotect.c:21:
   arch/x86/mm/wrprotect.c: In function 'protect_pte':
   arch/x86/include/asm/pgtable.h:461:21: error: too few arguments to function 'pte_mkwrite'
     461 | #define pte_mkwrite pte_mkwrite
         |                     ^~~~~~~~~~~
   arch/x86/mm/wrprotect.c:386:23: note: in expansion of macro 'pte_mkwrite'
     386 |                 pte = pte_mkwrite(pte);
         |                       ^~~~~~~~~~~
   arch/x86/include/asm/pgtable.h:460:7: note: declared here
     460 | pte_t pte_mkwrite(pte_t pte, struct vm_area_struct *vma);
         |       ^~~~~~~~~~~
   arch/x86/mm/wrprotect.c: In function 'wrprotect_uninit':
   arch/x86/mm/wrprotect.c:728:13: warning: variable 'ret' set but not used [-Wunused-but-set-variable]
     728 |         int ret;
         |             ^~~
   cc1: some warnings being treated as errors


vim +/ret +103 arch/x86/mm/wrprotect.c

    95	
    96	/* split_large_pages
    97	 *
    98	 * This function splits all large pages in straight mapping area into 4K ones.
    99	 * Currently wrprotect supports only 4K pages, and so this is needed.
   100	 */
   101	static int split_large_pages(void)
   102	{
 > 103		int ret;
   104		struct mm_walk_ops split_large_pages_walk_ops;
   105	
   106		memset(&split_large_pages_walk_ops, 0, sizeof(struct mm_walk_ops));
   107		split_large_pages_walk_ops.pud_entry = split_large_pages_walk_pud;
   108		split_large_pages_walk_ops.pmd_entry = split_large_pages_walk_pmd;
   109	
   110		mmap_write_lock(&init_mm);
   111		ret = walk_page_range_novma(&init_mm, PAGE_OFFSET, PAGE_OFFSET + DIRECT_MAP_SIZE,
   112			&split_large_pages_walk_ops, init_mm.pgd, NULL);
   113		mmap_write_unlock(&init_mm);
   114	
   115		return 0;
   116	}
   117	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  reply	other threads:[~2023-11-11  5:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-10 15:00 [RFC PATCH 0/4 v1] LPC materials: livedump Lukas Hruska
2023-11-10 15:00 ` [RFC PATCH 1/4 v1] crash/vmcore: VMCOREINFO creation from non-kdump kernel Lukas Hruska
2023-11-10 21:56   ` kernel test robot
2023-11-10 23:26   ` kernel test robot
2023-11-10 15:00 ` [RFC PATCH 2/4 v1] livedump: Add write protection management Lukas Hruska
2023-11-11  5:20   ` kernel test robot [this message]
2023-11-10 15:00 ` [RFC PATCH 3/4 v1] livedump: Add memory dumping functionality Lukas Hruska
2023-11-11 15:06   ` kernel test robot
2023-11-11 19:19   ` kernel test robot
2023-11-10 15:00 ` [RFC PATCH 4/4 v1] livedump: Add tools to make livedump creation easier Lukas Hruska

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=202311111350.ddmhyoBh-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=lhruska@suse.cz \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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.