All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Daniel Gomez <da.gomez@samsung.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH 11/11] shmem: add per-block uptodate tracking
Date: Sun, 29 Oct 2023 12:46:34 +0800	[thread overview]
Message-ID: <202310291218.fYLv1WWN-lkp@intel.com> (raw)
In-Reply-To: <20231028211518.3424020-12-da.gomez@samsung.com>

Hi Daniel,

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

[auto build test ERROR on akpm-mm/mm-everything]
[also build test ERROR on next-20231027]
[cannot apply to linus/master v6.6-rc7]
[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/Daniel-Gomez/XArray-add-cmpxchg-order-test/20231029-051730
base:   https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
patch link:    https://lore.kernel.org/r/20231028211518.3424020-12-da.gomez%40samsung.com
patch subject: [RFC PATCH 11/11] shmem: add per-block uptodate tracking
config: powerpc64-randconfig-003-20231029 (https://download.01.org/0day-ci/archive/20231029/202310291218.fYLv1WWN-lkp@intel.com/config)
compiler: powerpc64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231029/202310291218.fYLv1WWN-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/202310291218.fYLv1WWN-lkp@intel.com/

All error/warnings (new ones prefixed by >>):

>> mm/shmem.c:4673:29: error: 'shmem_invalidate_folio' undeclared here (not in a function); did you mean 'shmem_replace_folio'?
    4673 |         .invalidate_folio = shmem_invalidate_folio,
         |                             ^~~~~~~~~~~~~~~~~~~~~~
         |                             shmem_replace_folio
>> mm/shmem.c:4674:27: error: 'shmem_release_folio' undeclared here (not in a function); did you mean 'shmem_replace_folio'?
    4674 |         .release_folio  = shmem_release_folio,
         |                           ^~~~~~~~~~~~~~~~~~~
         |                           shmem_replace_folio
>> mm/shmem.c:4675:34: error: 'shmem_is_partially_uptodate' undeclared here (not in a function); did you mean 'shmem_set_range_uptodate'?
    4675 |         .is_partially_uptodate = shmem_is_partially_uptodate,
         |                                  ^~~~~~~~~~~~~~~~~~~~~~~~~~~
         |                                  shmem_set_range_uptodate
>> mm/shmem.c:212:13: warning: 'sfs_free' defined but not used [-Wunused-function]
     212 | static void sfs_free(struct folio *folio)
         |             ^~~~~~~~


vim +4673 mm/shmem.c

  4662	
  4663	const struct address_space_operations shmem_aops = {
  4664		.writepage	= shmem_writepage,
  4665		.dirty_folio	= noop_dirty_folio,
  4666	#ifdef CONFIG_TMPFS
  4667		.write_begin	= shmem_write_begin,
  4668		.write_end	= shmem_write_end,
  4669	#endif
  4670	#ifdef CONFIG_MIGRATION
  4671		.migrate_folio	= migrate_folio,
  4672	#endif
> 4673		.invalidate_folio = shmem_invalidate_folio,
> 4674		.release_folio	= shmem_release_folio,
> 4675		.is_partially_uptodate = shmem_is_partially_uptodate,
  4676		.error_remove_page = shmem_error_remove_page,
  4677	};
  4678	EXPORT_SYMBOL(shmem_aops);
  4679	

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

  parent reply	other threads:[~2023-10-29  4:46 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20230919135546eucas1p1181b8914fb5eceda5f08068802941358@eucas1p1.samsung.com>
2023-09-19 13:55 ` [PATCH v2 0/6] shmem: high order folios support in write path Daniel Gomez
2023-09-19 13:55   ` [PATCH v2 1/6] shmem: drop BLOCKS_PER_PAGE macro Daniel Gomez
2023-09-19 13:55   ` [PATCH v2 2/6] shmem: return freed pages in shmem_free_swap Daniel Gomez
2023-09-19 14:56     ` Matthew Wilcox
2023-09-19 13:55   ` [PATCH v2 3/6] shmem: account for large order folios Daniel Gomez
2023-09-19 13:55   ` [PATCH v2 4/6] shmem: add order parameter support to shmem_alloc_folio Daniel Gomez
2023-09-19 13:55   ` [PATCH v2 5/6] shmem: add file length in shmem_get_folio path Daniel Gomez
2023-09-20 18:03     ` kernel test robot
2023-09-19 13:55   ` [PATCH v2 6/6] shmem: add large folios support to the write path Daniel Gomez
2023-09-19 15:01     ` Matthew Wilcox
2023-09-19 16:28       ` Daniel Gomez
2023-09-20 17:41     ` kernel test robot
2023-09-25 20:39     ` kernel test robot
2023-10-28 21:15   ` [RFC PATCH 00/11] shmem: high order folios support in " Daniel Gomez
2023-10-28 21:15     ` [RFC PATCH 01/11] XArray: add cmpxchg order test Daniel Gomez
2023-10-29 20:11       ` Matthew Wilcox
2023-11-03 23:12         ` Daniel Gomez
2023-10-28 21:15     ` [RFC PATCH 02/11] test_xarray: add tests for advanced multi-index use Daniel Gomez
2023-10-28 21:15     ` [RFC PATCH 03/11] shmem: drop BLOCKS_PER_PAGE macro Daniel Gomez
2023-10-28 21:15     ` [RFC PATCH 04/11] shmem: return number of pages beeing freed in shmem_free_swap Daniel Gomez
2023-10-28 21:15     ` [RFC PATCH 05/11] shmem: account for large order folios Daniel Gomez
2023-10-29 20:40       ` Matthew Wilcox
2023-10-28 21:15     ` [RFC PATCH 06/11] shmem: trace shmem_add_to_page_cache folio order Daniel Gomez
2023-10-29 23:14       ` Matthew Wilcox
2023-10-28 21:15     ` [RFC PATCH 07/11] shmem: remove huge arg from shmem_alloc_and_add_folio() Daniel Gomez
2023-10-29 23:17       ` Matthew Wilcox
2023-10-28 21:15     ` [RFC PATCH 08/11] shmem: add file length arg in shmem_get_folio() path Daniel Gomez
2023-10-28 21:15     ` [RFC PATCH 09/11] shmem: add order arg to shmem_alloc_folio() Daniel Gomez
2023-10-31  7:04       ` Hannes Reinecke
2023-10-28 21:15     ` [RFC PATCH 10/11] shmem: add large folio support to the write path Daniel Gomez
2023-10-28 23:51       ` kernel test robot
2023-10-29 23:32       ` Matthew Wilcox
2023-10-28 21:15     ` [RFC PATCH 11/11] shmem: add per-block uptodate tracking Daniel Gomez
2023-10-28 23:51       ` kernel test robot
2023-10-29  4:46       ` kernel test robot [this message]
2023-10-29 20:43     ` [RFC PATCH 00/11] shmem: high order folios support in write path Matthew Wilcox

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=202310291218.fYLv1WWN-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=da.gomez@samsung.com \
    --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.