[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250901140515.15769-1-roypat@amazon.co.uk>
Date: Mon, 1 Sep 2025 14:05:16 +0000
From: "Roy, Patrick" <roypat@...zon.co.uk>
To: "lkp@...el.com" <lkp@...el.com>
CC: "ackerleytng@...gle.com" <ackerleytng@...gle.com>, "david@...hat.com"
<david@...hat.com>, "Manwaring, Derek" <derekmn@...zon.com>, "Thomson, Jack"
<jackabt@...zon.co.uk>, "Kalyazin, Nikita" <kalyazin@...zon.co.uk>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>, "kvmarm@...ts.linux.dev"
<kvmarm@...ts.linux.dev>, "linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>, "linux-mm@...ck.org" <linux-mm@...ck.org>,
"oe-kbuild-all@...ts.linux.dev" <oe-kbuild-all@...ts.linux.dev>,
"pbonzini@...hat.com" <pbonzini@...hat.com>, "Roy, Patrick"
<roypat@...zon.co.uk>, "rppt@...nel.org" <rppt@...nel.org>,
"seanjc@...gle.com" <seanjc@...gle.com>, "tabba@...gle.com"
<tabba@...gle.com>, "vbabka@...e.cz" <vbabka@...e.cz>, "will@...nel.org"
<will@...nel.org>, "Cali, Marco" <xmarcalx@...zon.co.uk>
Subject: Re: [PATCH v5 03/12] mm: introduce AS_NO_DIRECT_MAP
On Sun, 2025-08-31 at 11:26 +0100, kernel test robot wrote:
> Hi Patrick,
>
> kernel test robot noticed the following build warnings:
>
> [auto build test WARNING on a6ad54137af92535cfe32e19e5f3bc1bb7dbd383]
>
> url: https://github.com/intel-lab-lkp/linux/commits/Roy-Patrick/filemap-Pass-address_space-mapping-to-free_folio/20250828-174202
> base: a6ad54137af92535cfe32e19e5f3bc1bb7dbd383
> patch link: https://lore.kernel.org/r/20250828093902.2719-4-roypat%40amazon.co.uk
> patch subject: [PATCH v5 03/12] mm: introduce AS_NO_DIRECT_MAP
> config: loongarch-randconfig-r133-20250831 (https://download.01.org/0day-ci/archive/20250831/202508311805.yfcdeaFC-lkp@intel.com/config)
> compiler: loongarch64-linux-gcc (GCC) 14.3.0
> reproduce: (https://download.01.org/0day-ci/archive/20250831/202508311805.yfcdeaFC-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@...el.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202508311805.yfcdeaFC-lkp@intel.com/
>
> sparse warnings: (new ones prefixed by >>)
>>> mm/secretmem.c:155:39: sparse: sparse: symbol 'secretmem_aops' was not declared. Should it be static?
>
> vim +/secretmem_aops +155 mm/secretmem.c
>
> 1507f51255c9ff Mike Rapoport 2021-07-07 154
> 1507f51255c9ff Mike Rapoport 2021-07-07 @155 const struct address_space_operations secretmem_aops = {
> 46de8b979492e1 Matthew Wilcox (Oracle 2022-02-09 156) .dirty_folio = noop_dirty_folio,
> 6612ed24a24273 Matthew Wilcox (Oracle 2022-05-02 157) .free_folio = secretmem_free_folio,
> 5409548df3876a Matthew Wilcox (Oracle 2022-06-06 158) .migrate_folio = secretmem_migrate_folio,
> 1507f51255c9ff Mike Rapoport 2021-07-07 159 };
> 1507f51255c9ff Mike Rapoport 2021-07-07 160
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki
This is the same thing Mike already pointed out (making `secretmem_aops` static)
Powered by blists - more mailing lists