From: kernel test robot <lkp@intel.com>
To: Andrea Cervesato <andrea.cervesato@suse.de>,
Namjae Jeon <linkinjeon@kernel.org>,
Sungjong Seo <sj1557.seo@samsung.com>,
Yuezhang Mo <yuezhang.mo@sony.com>,
David Timber <dxdt@dev.snart.me>
Cc: oe-kbuild-all@lists.linux.dev, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, jack@suse.cz, chrubis@suse.cz,
Andrea Cervesato <andrea.cervesato@suse.com>
Subject: Re: [PATCH] exfat: implement swap activate
Date: Wed, 24 Jun 2026 10:54:39 +0800 [thread overview]
Message-ID: <202606241018.4N100hSQ-lkp@intel.com> (raw)
In-Reply-To: <20260618-exfat_swap_activate-v1-1-4c6a465df295@suse.com>
Hi Andrea,
kernel test robot noticed the following build errors:
[auto build test ERROR on e771677c937da5808f7b6c1f0e4a97ec1a84f8a8]
url: https://github.com/intel-lab-lkp/linux/commits/Andrea-Cervesato/exfat-implement-swap-activate/20260622-172327
base: e771677c937da5808f7b6c1f0e4a97ec1a84f8a8
patch link: https://lore.kernel.org/r/20260618-exfat_swap_activate-v1-1-4c6a465df295%40suse.com
patch subject: [PATCH] exfat: implement swap activate
config: microblaze-allyesconfig (https://download.01.org/0day-ci/archive/20260624/202606241018.4N100hSQ-lkp@intel.com/config)
compiler: microblaze-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260624/202606241018.4N100hSQ-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/202606241018.4N100hSQ-lkp@intel.com/
All errors (new ones prefixed by >>):
fs/exfat/inode.c: In function 'exfat_swap_activate':
>> fs/exfat/inode.c:556:16: error: implicit declaration of function 'generic_swapfile_activate' [-Wimplicit-function-declaration]
556 | return generic_swapfile_activate(sis, file, span);
| ^~~~~~~~~~~~~~~~~~~~~~~~~
vim +/generic_swapfile_activate +556 fs/exfat/inode.c
537
538 static int exfat_swap_activate(struct swap_info_struct *sis,
539 struct file *file, sector_t *span)
540 {
541 struct inode *inode = file_inode(file);
542 struct exfat_inode_info *ei = EXFAT_I(inode);
543 int ret;
544
545 /*
546 * exfat's fallocate allocates clusters without updating valid_size,
547 * leaving them invisible to bmap(). Extend valid_size to i_size so
548 * that generic_swapfile_activate() can map all blocks.
549 */
550 if (ei->valid_size < i_size_read(inode)) {
551 ret = exfat_extend_valid_size(inode, i_size_read(inode));
552 if (ret)
553 return ret;
554 }
555
> 556 return generic_swapfile_activate(sis, file, span);
557 }
558
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-06-24 2:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 9:33 [PATCH] exfat: implement swap activate Andrea Cervesato
2026-06-18 18:15 ` David Timber
2026-06-18 19:59 ` David Timber
2026-06-25 13:56 ` Andrea Cervesato
2026-06-24 2:54 ` kernel test robot [this message]
2026-06-24 6:02 ` 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=202606241018.4N100hSQ-lkp@intel.com \
--to=lkp@intel.com \
--cc=andrea.cervesato@suse.com \
--cc=andrea.cervesato@suse.de \
--cc=chrubis@suse.cz \
--cc=dxdt@dev.snart.me \
--cc=jack@suse.cz \
--cc=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sj1557.seo@samsung.com \
--cc=yuezhang.mo@sony.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